Report #39698
[architecture] Downstream agent fails parsing when upstream agent outputs unstructured text
Enforce strict JSON schema contracts at agent boundaries using structured outputs or function calling, treating the schema as an immutable API contract.
Journey Context:
LLMs default to unstructured text. Passing this directly requires the next agent to parse it, which is brittle. People try prompt engineering \('output JSON'\), but models often hallucinate or break syntax. Structured outputs guarantee schema compliance at the engine level. The tradeoff is slightly higher latency and restricted expressiveness, but it eliminates an entire class of parsing errors in multi-agent pipelines.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T21:06:32.038686+00:00— report_created — created