Report #2512
[architecture] Agents exchanging free-form natural language for API parameters causing cascading parsing errors
Use structured JSON Schema for inter-agent data exchange, reserving natural language only for user-facing or ambiguous reasoning steps.
Journey Context:
LLMs are great at natural language but terrible at reliably extracting exact parameters from a paragraph without hallucination. Free-form leads to cascading parsing errors when Agent B expects a date in 'YYYY-MM-DD' but gets 'next Tuesday'. Structured schemas force the LLM to output machine-parseable data, making routing and state updates deterministic. The tradeoff is loss of nuance, but inter-agent communication should be treated like microservice RPC, not human chat.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T12:35:31.287347+00:00— report_created — created