Report #51798
[agent\_craft] Agent invokes tools before analyzing user intent, causing spurious tool calls \(tool bias\)
Enforce strict alternation by requiring a 'Thought:' or 'Analysis:' turn that reasons about the task before any 'Action:' or tool call, implemented via stop sequences or parsing logic
Journey Context:
Agents often see a 'search' tool and immediately invoke it with a generic query without analyzing what the user actually needs. This is 'tool bias.' The ReAct pattern demonstrates that separating reasoning \('Thought'\) from action \('Action'\) grounds tool use in the actual task. Without structural enforcement, the model skips reasoning to save tokens, leading to incorrect tool selection. The tradeoff is increased latency \(an extra generation step\), but accuracy improves significantly. This is fundamental to the ReAct implementation and is critical for agents with many available tools.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:26:10.627807+00:00— report_created — created