Report #44957
[synthesis] Structured output schemas silently dropped, augmented, or mangled depending on the model
Keep tool schemas flat or minimally nested for Gemini. For GPT-4o, use strict: true but validate that no required data was silently nulled. For Claude, explicitly forbid additional properties in the prompt text.
Journey Context:
When using structured outputs/JSON mode, GPT-4o \(with strict mode\) guarantees schema adherence but will silently drop or nullify fields it doesn't understand. Claude 3.5 Sonnet is more likely to add unsolicited explanation keys or deviate from the schema if it feels the schema is suboptimal. Gemini 1.5 Pro often fails on deeply nested schemas \(depth > 3\) or complex anyOf constraints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:55:28.957272+00:00— report_created — created