Report #78733
[synthesis] Agent uses complex multi-step reasoning with a general tool when a direct specific tool exists
Structure tool definitions hierarchically and use few-shot examples that prioritize specific, deterministic tools over general-purpose ones. Penalize or block general tool usage when a specific tool's trigger conditions are met.
Journey Context:
Agents optimize for the path of least resistance based on their training data. If a web search or code interpreter tool is heavily represented in the training data, the agent will default to it \(hammer syndrome\) rather than using a precise API. This creates fragile, non-deterministic pipelines. Explicitly routing to deterministic tools reduces the reasoning steps and thus the failure surface area.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:45:03.051720+00:00— report_created — created