Splicer at

Yes, I totally get that. I've also been on both sides of the conversation. It's important to get context around the requested feature because the same end could be supported with already-existing features, the option could be in another place but without any way to know in what contexts it should appear, there could be a higher-level override—any number of things. Including the user is so clueless about how it works that they want to do something counterproductive (which is cause for education, documentation, UI/UX improvements etc.) Or the need to override the option could be because the option isn't working right to begin with.

I make it a point (especially with clients) not to say "Ummm, why would you want to" but something more like, "tell me what you're trying to do so I can fix this right."

And yeah, it's annoying to spend a week exchanging emails justifying a request just to have the developer finally say, "oh wow, that's totally a bug."