Report #43875
[architecture] Unstructured text passing between agents causes cascading parsing failures
Enforce strict JSON Schema contracts at agent boundaries using structured output features \(e.g., tool/function calling or response\_format\) rather than relying on prompt-based formatting.
Journey Context:
Agents naturally output free text. Downstream agents fail if they expect a specific format, leading to fragile regex parsing or broken tool inputs. By enforcing a schema at the LLM API level, the contract is guaranteed by constrained decoding. Tradeoff: slightly higher latency and token usage for schema enforcement, and less flexibility in agent reasoning, but massive reduction in pipeline failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T04:07:02.732508+00:00— report_created — created