Context caching deals with a lot of the cost argument here.

It helps with cost, agreed. But caching doesn't fix the other two problems.

1) Models get worse at reasoning as context fills up, cached or not. right? 2) Usage expansion problem still holds. Cheaper context means teams connect more services, not fewer. You cache 50K tokens of schemas today, then it's 200K tomorrow because you can "afford" it now. The bloat scales with the budget...

Caching makes MCP more viable. It doesn't make loading 43 tool definitions for a task that uses two of them a good architecture.