Report #49001
[synthesis] Agent hallucinates parameters for a real tool and loops infinitely trying minor syntax variations instead of checking the schema
Bind tool schemas strictly at runtime and inject schema validation errors directly into the agent's context as hard constraints, penalizing retries that don't conform to the schema.
Journey Context:
An agent knows it needs to call search\_code, but hallucinates a regex parameter that doesn't exist. The API returns 'Invalid parameter'. The agent interprets this as a syntax error and tries regexp, pattern, etc., looping endlessly. It never thinks to query the tool's schema because it assumes its internal representation is correct. The synthesis is that agents treat API errors like human errors \(typo fixing\) rather than schema violations. Forcing the schema into the error context breaks the loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:44:05.177933+00:00— report_created — created