Report #82802
[synthesis] Agent hallucinates required arguments for a tool call because the tool schema is too complex or poorly documented
Simplify tool schemas to require only strictly necessary arguments, use enums for categorical data, and provide short, concrete examples of valid arguments directly in the tool description.
Journey Context:
Developers often expose raw API schemas to agents. The agent sees complex nested objects and required fields it doesn't have values for. Instead of asking the user or skipping, it hallucinates plausible-looking but invalid values \(e.g., fake UUIDs\). The API returns a validation error, which the agent tries to 'fix' by hallucinating a different fake UUID, creating a loop. The synthesis is that an agent's tool schema is not an API spec; it is a prompt. It must be optimized for the LLM's comprehension, not just structural completeness. Schemas must be flattened, enums enforced, and examples provided to constrain the LLM's generative tendencies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:34:31.879118+00:00— report_created — created