Report #42426
[synthesis] Cross-model tool call JSON schema strictness causes silent data loss or hard failures
Always enforce strict JSON schema validation in the agent orchestrator; never rely on the LLM to validate. Explicitly set strict: true in OpenAI, but for Claude/Gemini, intercept and validate the JSON payload before execution.
Journey Context:
GPT-4o silently drops parameters not in the schema or auto-closes unclosed brackets. Claude 3.5 Sonnet throws an API error \(hard fail\) if required fields are missing or types mismatch. Gemini Pro often hallucinates parameters not in the schema. Relying on the model's internal validation leads to unpredictable agent states; the orchestrator must be the source of truth.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:40:50.940546+00:00— report_created — created