AI agent tool sprawl quietly inflates automation costs. See how Anthropic's 2026 MCP upgrades cut context bloat and add real access control.
Most businesses that adopt AI agents start small: one agent watching a WhatsApp inbox, or one agent pulling leads into a CRM. Then it works, and the natural next step is to connect that agent to more systems: inventory, calendar, billing, a support desk, a reporting tool. Each new connection is usually built as an MCP (Model Context Protocol) server, and each one adds its own set of tool definitions that the model has to read before it can do anything.
This is where AI agent tool sprawl quietly becomes a real operating cost. Every tool definition your agent can call sits in its context window on every single request, whether that request needs the tool or not. An agent connected to five MCP servers can be carrying tens of thousands of tokens of tool definitions before it has processed a single instruction from a user. That's money spent and latency added on every call, and it gets worse every time you plug in one more integration.
Anthropic shipped two updates in the past year that speak directly to this problem: a way to stop paying for tools you're not using, and a way to control who's allowed to use them in the first place. Both matter if you're running, or planning to build, AI agents that touch real business systems.
According to Anthropic's engineering documentation on advanced tool use, a Claude-based agent connected to just five MCP servers can see tool definitions consuming roughly 55,000 tokens before the conversation even starts. That's context spent on definitions the agent may never call in a given turn, on every single request, for the life of the agent.
The knock-on effect isn't just cost. It's accuracy. Anthropic's own benchmarking, published alongside the feature, found that loading too many tool definitions at once actively hurts a model's ability to pick the right one and fill it in correctly. The fix they shipped, the Tool Search Tool, changes how tools are loaded in the first place: instead of handing the model every tool definition up front, you mark tools with a defer_loading flag, and the model sees only the Tool Search Tool itself plus whatever it uses most often. It then searches for the specific tool it needs, on demand, in the moment it needs it.
The reported numbers are substantial. With Tool Search Tool enabled, that same five-server setup drops from roughly 55,000 tokens of upfront definitions to about 8,700, an 85 percent reduction, while still preserving access to the full tool library. Accuracy moved in the same direction: Anthropic reported Opus 4 improving from 49 percent to 74 percent on a tool-selection benchmark with the feature enabled, and Opus 4.5 improving from 79.5 percent to 88.1 percent. This shipped as a real feature (accessible via a beta header) in Anthropic's November 2025 advanced tool use release, not a roadmap item.
Tool Search Tool is the