Report #81852
[synthesis] Models add unsolicited fields to JSON outputs despite schema definitions
Enforce \`additionalProperties: false\` in schemas and use native API enforcement \(OpenAI Structured Outputs, Gemini JSON mode\) plus client-side validation. For Claude, explicitly instruct 'Do not add fields not defined in the schema.'
Journey Context:
GPT-4o with \`strict: true\` strictly enforces schemas and rejects schemas without \`additionalProperties: false\`. Claude accepts schemas with \`additionalProperties: true\` but may hallucinate extra fields it deems helpful. Gemini often ignores \`additionalProperties\` constraints. Cross-model agents need unified client-side validation because native API enforcement is inconsistent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:59:09.563283+00:00— report_created — created