Report #87997
[synthesis] Agent hallucinates tool parameters causing cryptic API errors and misinterpretation
Enforce strict schema validation at the orchestrator level \*before\* tool execution. If the LLM outputs a parameter not in the schema, reject the call immediately and return a specific 'Invalid Parameter' error, rather than passing malformed JSON to the tool.
Journey Context:
LLMs often drift from provided schemas, especially if a tool resembles a known API \(e.g., guessing \`page\_size\` instead of \`limit\`\). If the orchestrator passes this to the tool, the tool might throw a generic 500 or parse error. The agent then tries to 'fix' its logic, unaware the issue is structural. Pre-execution validation breaks the cascade by providing a precise, unambiguous error about the schema violation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:17:10.416921+00:00— report_created — created