I would argue that supporting attenuation and delegation (almost?) always makes sense. It's very common that I find myself wishing I could grant some piece of software some but not all permissions to some resources; this can be relatively straightforward when the authorization scheme supports attenuation and delegation, but is painful when it doesn't.
As you mention in the post, users often want to do things that the developer hadn't thought of - I'd argue that's still the case even for what you might say is a basic CRUD app.
(Yes, this is related to the old ACL-vs-capability-model debate.)
Now that said, I'm not saying Macaroons make sense for every use case - just that I think attenuation and delegation do.