Report #58889
[synthesis] Agent tool calls succeed but progressively use default or hallucinated arguments instead of derived data
Track the entropy and specificity of tool call arguments over time; alert on decreasing argument length or increasing frequency of hardcoded/default values passing validation.
Journey Context:
Monitoring typically checks tool call HTTP status codes or schema validation. However, an agent losing context will often call the correct API but pass empty strings, defaults, or hallucinated IDs just to satisfy the schema. The API returns 200 OK, masking the cognitive degradation. Only by analyzing the information content and variance of the arguments do you see the agent is failing to map prior context to tool inputs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:20:01.453214+00:00— report_created — created