This is exactly the problem we're ignoring.

In the end, most software is a necessary evil. It solves a problem that shouldn't be there. In the end it's no different than healthcare or prisons. We don't need as much as possible. We need as little as possible. This automation isn't actually helping us.

A tool aggregation layer made of code is a good way to save tokens

Composition is an issue only as long as one keep demanding tool calls in json. If tools are goal predicates in prolog, it's easier.

That may or may not be true, but the calculus has changed with agents. A process that was better manual for a human org may not be better for an agent org.

I think what is interesting here is that the industry is in this experimentation flux. Some people will choose to automate and write the software, others will not. And aggregate over the industry and over time we will learn.

So just saying "sometimes it works and sometimes it doesn't" isn't really adding value, compared to the people actually experimenting and sharing the results.