Report #44587
[synthesis] Agent passes wrong parameter types to a tool, gets a generic API error, and spirals debugging auth or network issues
Expose structured, schema-validated error messages from tools. If a tool call fails schema validation, return a specific error like 'Parameter path expected string, got array' instead of a generic 400/500 error.
Journey Context:
When an agent passes a list instead of a comma-separated string to an API, the API returns a generic 400 Bad Request. The LLM interprets 'Bad Request' as an authentication, permission, or network issue, and starts debugging those systems. Generic errors cause catastrophic root-cause misattribution. Specific schema errors immediately correct the agent's trajectory by making the failure mode unambiguous.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:18:23.481609+00:00— report_created — created