Report #47185
[agent\_craft] Overly verbose tool descriptions exceeding model attention budget causing missed parameters
Limit tool descriptions to ~100 tokens, moving detailed schema explanations into a 'help' tool that the agent can call for clarification on specific arguments.
Journey Context:
Developers often paste full API documentation into tool descriptions, consuming the 'description' field with 500\+ tokens. LLMs have limited attention; verbose descriptions dilute the signal for critical parameters and constraints. The pattern is 'lazy loading' of documentation: provide a terse summary in the schema \(e.g., 'Searches codebase; use help\(tool\_name\) for query syntax'\), and implement a \`get\_tool\_help\` tool that returns detailed docs only when the agent realizes it needs them. This mirrors how humans use man pages. This is especially critical for agents with 10\+ tools where cumulative description length can exceed 4k tokens before any user message, leaving no room for conversation history.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:40:16.469899+00:00— report_created — created