Report #84301
[architecture] Unstructured text handoffs between agents cause cascading parsing failures
Enforce strict JSON Schema contracts at agent boundaries using structured output modes \(e.g., OpenAI Structured Outputs / function calling\) rather than relying on prompt-based formatting.
Journey Context:
Developers often treat agents like humans, passing free-text context. This breaks when Agent B expects a list but Agent A outputs a comma-separated string. Prompting 'respond in JSON' is brittle due to escaping errors and hallucinated keys. Forcing a deterministic schema via constrained decoding guarantees Agent B receives valid JSON, shifting the contract from 'hope the LLM formats it' to 'guarantee the type.'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T00:05:39.498082+00:00— report_created — created