Here is another scenario: the client, or a team member, wants a better page speed score and wants to know how much time it will take to improve it.
There are many similar examples, but not everything is about estimation. Sometimes “it depends” answer means choosing the right technologies or prioritizing tasks or anything that requires planning and organizing a series of actions to come up to a solution. Unless the task or request is something trivial, it automatically brings many questions to the table.
Asking the right questions and understanding the problem is the job-half-done. That is where the experience steps in. Experienced developers ask questions to help the client understand the request and guide the client to the solution. Non-experienced developers should learn how to ask these questions.
What the “it depends” answer means, in a nutshell, is that the task is not very well defined. That leads us to the actual problem. If the person who assigns the tasks knows the possibilities of how to resolve the task, there wouldn’t be “it depends” answers. But not everyone understands these possibilities. And that is ok.