Tool use / function calling
ReAct
ReAct: Synergizing Reasoning and Acting in Language Models
Heavily superseded — a standard baseline that newer methods routinely beat
6 papers critique it · 4 beat it on benchmarks
What papers say
Verbatim critique sentences, each from a paper that cites ReAct as a baseline.
ReAct~Yao2023ReAct, Auto-GPT~Richards2023AutoGPT, and GAIA~mialon2023gaia explored the interaction between reasoning and acting, though often in synthetic or text-only environments
“ReAct combines reasoning with API calls for multi-step tasks, but its performance is constrained by pretraining and degrades with increased tool complexity.”
“These results imply that curated data and retrieval augmentation, not sheer parameter count, are the present keys to dependable LLM tool use.”
“they operate at the agent level rather than providing fine-grained reasoning for individual function parameters”
“The dominant approach for orchestrating tool usage relies on reactive, step-by-step reasoning frameworks like ReAct, often augmented by self-reflection techniques. However, this paradigm suffers from inherent local optimization traps due to its incremental decision-making process. While potentially effective for simple queries, its reactive nature often falters on complex tasks.”
“These studies substantially advance reasoning control and tool-use alignment, but they generally treat reasoning depth and execution structure as separate concerns rather than as jointly case-conditioned aspects of the same problem.”
Beaten on benchmarks
Head-to-head results where a newer method reports beating ReAct. Values are copied from the source paper's tables — verify against the cited paper.
Qwen2.5-7B-Instruct-CAST beats ReAct
79.43 vs 18.22
ToolBench Win · [Qwen2.5-7B-Instruct]
Case-Based Calibration of Adaptive Reasoning and Execution for LLM Tool UseReAct-TS-Flow (TS-Guard) beats ReAct
95.45 vs 42.04
Refusal · [Qwen2.5-14B-Instruct as Agent Backbone, AgentHarm]
ToolSafe: Enhancing Tool Invocation Safety of LLM-based agents via Proactive Step-level Guardrail and Feedback
What to use instead
Recent methods in the same sub-problem, not yet superseded in the knowledge base — arXiv benchmark leaders, not vetted production recommendations.