Just think of a function which generates a random number for a lottery app. Do you want to call the function 'generateRandomNumber' or 'generateLotteryNumber'? There is no reason to constrain your function to the 'lottery' use case when it could also serve an infinite number of other use cases.
The function which is used as a dependency shouldn't concern itself with the specific business case towards which it will be applied.
As you move towards the leaves of the dependency hierarchy, the abstraction becomes more about technology and less about business domain.