PulseAugur
EN
LIVE 17:06:56

Analysis shows input schemas, not descriptions, are largest part of tool definitions

A recent analysis of five servers and 68 tools revealed that input schemas constitute the largest portion of tool definitions, not descriptions as previously suggested. While descriptions account for about 11.2% of tokens, input schemas make up nearly 30%, and output schemas around 9.5%. The memory server was an exception where the output schema was slightly larger than the input schema, but contrary to prior assumptions, these schemas were author-written and not generated from past runs. This suggests that efforts to reduce definition bloat by trimming descriptions are misdirected, as the primary cost lies elsewhere in the schema definitions. AI

IMPACT This analysis highlights potential inefficiencies in how AI tools are defined, suggesting that optimizing input and output schemas could be more impactful than trimming descriptions for reducing bloat.

RANK_REASON Analysis of technical implementation details regarding token usage in tool definitions. [lever_c_demoted from research: ic=1 ai=0.7]

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Analysis shows input schemas, not descriptions, are largest part of tool definitions

How we ranked this

Signal score
33 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
Analysis of technical implementation details regarding token usage in tool definitions. [lever_c_demoted from research: ic=1 ai=0.7]
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
infra
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · AheadKit ·

    Stop Trimming Tool Descriptions. They Were Never the Biggest Part.

    <p>kevinhall left a comment on my piece about the 200-tool menu, and it pointed at the one split my run never made. He had measured real hosted tools, and the heaviest definition he found was almost all an output schema the server had made up from past runs, nothing the author wr…