Budget-Aware Tool Use Enables Effective Agent Scaling
Agent scaling is not just more tokens or tool calls; agents must know and strategically allocate their remaining budget.
Key takeaway
Budget Tracker adds explicit resource state to the agent loop, while BATS adds adaptive planning and verification; under a 100-call-per-tool budget, Gemini-2.5-Pro with BATS reaches 24.6% BrowseComp, 46.0% BrowseComp-ZH, and 27.0% HLE-Search.
Updated on Oct 2, 2026
01
Abstract
Tool-augmented agents scale along two dimensions: internal reasoning tokens and external tool calls. This paper shows that simply increasing tool-call budgets can hit a performance ceiling because agents do not adapt their behavior to remaining resources. It introduces Budget Tracker for explicit resource awareness and BATS (Budget-Aware Test-time Scaling) for adaptive planning and verification, using a unified cost metric that combines token and tool costs.
02
Introduction
Test-time scaling has improved language-model reasoning, but tool-using agents incur a second resource cost: interaction with the external environment. Search-heavy agents may spend resources on repeated or low-yield paths, so a larger interaction budget does not guarantee better answers. The paper studies how agents should allocate a fixed resource budget between exploration, verification, and additional reasoning.
03
Problem
The central problem is budget-blind tool use. A conventional agent may continue a weak search path, terminate before exploiting useful budget, or incur tool costs without proportional accuracy gains. The paper formulates agent scaling under explicit per-tool budgets and asks how an agent can use remaining resources strategically instead of treating the budget as a passive limit.
04
Background
Agent test-time scaling extends ordinary inference-time reasoning into environments where models can act through tools. In this setting, resource consumption is heterogeneous: tokens represent internal computation, while tool calls consume external services and interaction opportunities. The paper focuses on web-search agents and studies scaling as a cost-performance problem rather than measuring accuracy alone.
05
Methodology
Two methods are introduced. Budget Tracker is a lightweight plug-in that exposes policy guidance and current/remaining resource usage inside the agent context. BATS builds on this state with a persistent tree-structured plan, explicit exploration-versus-verification decomposition, trajectory summarization, and self-verification. The verifier classifies a candidate path as SUCCESS, CONTINUE, or PIVOT, allowing the agent to deepen a promising lead or abandon an unproductive one.
Budget Tracker in the agent loop
Original arXiv HTML figure showing budget state supplied before the next reasoning and tool call.
arXiv HTML v2
Budget-aware scaling curve
Original arXiv HTML plot showing ReAct saturating while Budget Tracker continues to scale with more tool budget.
arXiv HTML v2
BATS framework
Original arXiv HTML figure showing budget-aware planning, tool execution, verification, pivoting, and answer selection.
arXiv HTML v2
Formula notes
Mathematical details
Budget-constrained accuracy
The agent maximizes expected accuracy while never exceeding the allocated call budget for any tool.
- y
- -ground-truth answer
- pi
- -agent policy
- b_i
- -maximum calls for tool i
- c_i
- -realized calls for tool i
- yhat
- -agent answer
Unified agent cost
Total economic cost combines token consumption with the cost of each realized tool invocation.
- K
- -number of tools
- P_i
- -economic price per call
- c_i
- -number of calls to tool i
- c_token
- -token cost
06
Architecture
The reported system is a ReAct-style search agent with Search and Browse tools. Budget Tracker inserts resource state into the reasoning loop. BATS wraps that loop with planning, execution, self-verification, summarization, and candidate selection. The architecture is training-free in the reported BATS experiments: the main change is how inference-time resources and trajectories are managed.
07
Dataset
The evaluation covers search-intensive and agent benchmarks: BrowseComp (1,266 questions), BrowseComp-ZH (289), HLE-Search (200), and a 114-task retail subset of tau2-bench. The repository identifies a 200-question BrowseComp subset used in the paper’s controlled comparisons.
08
Training
BATS does not introduce a new model-training objective in the reported experiments. The approach operates at test time by changing the agent’s planning, resource awareness, verification, and candidate-selection behavior. This makes the method applicable as an inference-time control layer around an existing tool-using model.
09
Experiments
The experiments vary available tool budgets and compare standard ReAct behavior, Budget Tracker, and BATS. Budget Tracker is evaluated across models under matched budgets. BATS is evaluated at 100 calls per tool and through ablations of planning and verification. The experiments measure both answer accuracy and resource consumption rather than accuracy in isolation.
Evidence highlights
- 01Matched-budget comparisons
- 02100-call-per-tool BATS setting
- 03Planning ablation
- 04Verification ablation
- 05Cost analysis
10
Baselines
The comparisons include ReAct as the principal budget-unaware agent baseline, together with SLIM and training-based agent approaches in the broader BATS experiments. The study also compares against different tool-allocation strategies to separate the value of explicit budget awareness from simply increasing the number of available interactions.
Evidence highlights
- 01ReAct
- 02SLIM
- 03Training-based agents
- 04Alternative scaling strategies
11
Results
Result board
Budget Tracker
Reported value12.8%12.6%
Result
40.4% fewer search calls
Result
19.9% fewer browse calls
Result
31.3% lower cost
BATS
24.6% / 46.0% / 27.0%
12
Ablation
Result board
Full BATS
18.7 / 39.1 / 23.0
No planning
17.0 / 34.6 / 20.0
No verification
15.4 / 37.7 / 22.0
Neither
14.6 / 32.9 / 21.5
13
Limitations
The framework focuses on explicit tool-call budgets and does not fully solve multidimensional resource allocation. Token cost, latency, concurrency, and tool reliability can interact with the call budget. The method also depends on the quality of the underlying model, search environment, verifier, and retrieved evidence. Benchmark improvements therefore do not by themselves establish production reliability across arbitrary agent workloads.
14
Conclusion
The paper’s central finding is that effective agent scaling requires resource awareness, not merely a larger tool-call allowance. Budget Tracker makes resource state visible; BATS uses that state to change exploration, verification, and stopping decisions. Together they improve the cost-performance frontier in the evaluated search-agent settings.
15
References
Tengxiao Liu et al., “Budget-Aware Tool-Use Enables Effective Agent Scaling,” arXiv:2511.17006, subsequently published at COLM 2026. Primary project repository: google-research/budget-aware-agent.
Source trail
Primary papers, implementation pages, and external source records used to ground this explainer.
ReAct: Synergizing Reasoning and Acting in Language Models
Base reasoning/action loop used by the search-agent experiments.
BrowseComp: A Simple Yet Challenging Benchmark for Browsing Agents
Primary browsing benchmark used in the experiments.
Lost in the Maze: Overcoming Context Limitations in Long-Horizon Agentic Search
SLIM baseline for context-efficient long-horizon search.
01arXiv v202arXiv HTML v203Official GitHub repositoryContinue reading
Related research
GitSwarm
GitSwarm turns inference-time work into a persistent, branchable body of reusable contributions that later agents can build on.
AI AgentsLongHarness
LongHarness helps agents reason over 100M-token document collections by keeping evidence and conclusions as explicit, revisable states that guide one another.
AI AgentsGenerative Agents
An agent architecture combining memory, retrieval, reflection, and planning to simulate believable long-horizon behavior.