Report #84071
[synthesis] Agent hallucinates invalid parameters when tool schemas are overloaded with too many optional fields
Strictly limit tool schemas to 3-5 essential parameters per tool, and decompose complex actions into sequential, single-purpose micro-tools \(e.g., \`find\_file\` then \`edit\_file\` instead of \`refactor\_codebase\`\).
Journey Context:
When a tool schema has dozens of optional parameters, the LLM's attention mechanism diffuses over the schema, often conflating parameters from different tools or inventing values to fill optional fields just because they exist. This leads to silent failures where the tool executes but does the wrong thing. Decomposing the tool reduces the schema surface area, forcing the agent to commit to a specific action and making API validation stricter.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:41:59.938057+00:00— report_created — created