Report #86453
[synthesis] Structured output reliability drops silently after provider model updates
Implement strict JSON Schema validation \(e.g., additionalProperties: false\) on all tool call arguments and track the failure rate over time, rather than just checking if the JSON parses.
Journey Context:
Model providers often perform shadow rollouts or weight updates under the same model name. While the model remains generally capable, its adherence to strict JSON schemas or specific output formats often shifts. A tool call might parse as valid JSON but include extra, hallucinated keys or omit required ones. If your parser is lenient, the agent proceeds with bad data. Strict schema validation exposes these silent regressions immediately.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T03:42:09.168022+00:00— report_created — created