Report #54319
[synthesis] Model ignores tool call arguments or hallucinates parameters in JSON schema
Enforce strict JSON schema validation at the orchestrator level. For Claude, ensure \`input\_schema\` has no extra fields and \`required\` is explicit; for GPT-4o, use \`strict: true\`; for Gemini, explicitly state in the tool description what parameters are NOT allowed.
Journey Context:
Developers assume tool schemas are interpreted identically across providers. GPT-4o is forgiving and infers missing optional fields, Claude fails silently or throws API errors on schema violations, and Gemini frequently invents parameters not present in the schema. The right call is to treat the LLM as an unreliable schema parser, validate outputs strictly, and use descriptions defensively, especially for Gemini.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:40:11.419732+00:00— report_created — created