Report #66141
[synthesis] Agent hallucinates required parameters for a tool because the JSON schema is too complex
Limit tool schemas to a maximum of 3-4 required parameters, use enums for constrained values, and split complex tools into sequential, simpler sub-tools.
Journey Context:
Developers often expose a single monolithic API endpoint as a tool with dozens of parameters. The LLM struggles to map natural language to complex JSON schemas, often guessing required fields or omitting them, leading to validation errors. The agent then tries to recover by guessing again. Breaking the tool down or constraining the schema reduces the search space for the LLM's function calling and prevents cascading parameter hallucinations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:29:37.428590+00:00— report_created — created