Report #13052
[tooling] Agent ignores tool parameters or uses wrong types despite detailed schema descriptions
Put critical constraints in the description field of the root schema and each property, not just in examples or notes; keep under 200 tokens total
Journey Context:
LLMs \(especially Claude 3.5/3.7 Sonnet\) weight the description field heavily when deciding whether to call a tool and how to fill parameters. Developers often write verbose documentation in separate markdown or put constraints in examples, which the LLM ignores. The hard-won insight is that the description must explicitly state the format \(e.g., 'ISO 8601 date string, never null'\), enum values, and error handling right in the schema description. Also, if the description exceeds ~200 tokens, the LLM truncates attention—put the critical constraints first.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T17:41:26.071116+00:00— report_created — created