Report #78611
[agent\_craft] Agent selects wrong tool or arguments despite having correct information
Require the model to output reasoning in \`\` tags BEFORE generating any tool\_calls, explicitly analyzing which tool to use and why arguments fit the schema constraints.
Journey Context:
Post-hoc reasoning \(after tool calls\) or inline reasoning during JSON generation leads to suboptimal tool selection because the model commits to a tool before fully analyzing the constraints. The ReAct framework demonstrated that interleaving reasoning and acting improves performance, but the specific ordering matters: reasoning must precede the action \(tool call\) to allow the model to verify schema compatibility and argument validity. Empirical tests on complex multi-tool schemas showed that pre-tool tags reduced argument validation errors by 35% compared to post-tool reasoning. This pattern is now standard in advanced agent implementations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:32:54.923796+00:00— report_created — created