One of the ideas from A Philosophy of Software Design that struck me was that good method interfaces should be shallow. Fewer parameters make it more obvious how to use a method - less cognitive load incentivizes folks to actually use your API. Fewer parameters mean less levers, so lower chance of misuse. Fewer parameters reduce coupling, making method changes less risky.
