Tool Definition Bloat: The Hidden Cost for Agents
TheZachMueller · x · 2026-07-19
The author shares a viewpoint from the Kimi team: when an application requires many tools, dumping them all into the top-level tools field causes "Tool Definition Bloat." Every request then carries the descriptions and parameter schemas for all tools, leading to significant token waste.
Furthermore, the more tool candidates there are, the easier it is for the model to choose the wrong one or generate invalid parameters. The post includes an image of a toolbox with 30+ bits where only 5 are actually used, perfectly illustrating this redundancy.
More from coding & agent
- ThoughtSpot launches SpotterCode, a hosted MCP server letting Claude Code query live instances — thoughtspotdev · 2026-10-26
- Non-developer stuck at 65% with Claude Code: rules files and CLAUDE.md weren't enough — jinguh · 2026-10-26
- HermesOBD: open-source macOS app pipes live car OBD-II data to a local Hermes agent — Teknium · 2026-10-26
- User Claims Codex Autonomously Reverse-Engineered Serum2 and Stripped Its License — Kyrannio · 2026-10-26
- colab-mcp lets AI agents control Google Colab notebooks directly — helloiamleonie · 2026-10-26
- Postiz, an open-source AI-agent social media manager, hits 37.9k GitHub stars — abhishek__AI · 2026-10-26