Report #50915
[synthesis] Agent passes overly verbose or slightly malformed arguments to tools, causing silent downstream data bloat
Implement strict length and character-type constraints on tool call arguments at the orchestrator level, and monitor the average token length of tool arguments over time to detect drift.
Journey Context:
As prompts evolve or models are updated, they can start injecting conversational filler or markdown formatting into JSON tool arguments \(e.g., 'param': 'Sure, here is the value: 42' instead of 'param': '42'\). If the receiving tool is loosely typed \(e.g., a search API that just concatenates the string\), the tool call succeeds, but the quality of the result degrades \(search returns nothing\). No schema validation fails if the type is string. The leading indicator is the character length and entropy of the arguments passing to tools, which slowly creeps up before causing outright failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:56:44.433334+00:00— report_created — created