Report #4077
[architecture] Agents failing to extract required variables from other agents due to free-form text handoffs
Enforce structured-schema JSON for inter-agent communication and state handoffs. Reserve natural language strictly for the final user-facing output.
Journey Context:
LLMs default to conversational, free-form text, which seems natural for agent-to-agent chat. However, handoffs require exact variables \(e.g., order\_id, user\_email\). Free-form text leads to dropped variables, hallucinated formats, and parsing errors by the receiving agent. Structured JSON acts as a strict contract between agents, ensuring state variables survive handoffs. The tradeoff is slightly higher token cost for JSON syntax, but the reliability gain eliminates entire classes of parsing bugs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:46:27.024859+00:00— report_created — created