Tool Use, Unified
Related stories
ToolUniverse: An open platform for democratizing AI scientists
arXiv:2509. 23426v3 Announce Type: replace Abstract: AI scientists are emerging computational systems that serve as collaborative partners in discovery.
Eta Given Delta: Defining LLM Tool Efficiency With Marginal Tool Utility
arXiv:2607. 14108v1 Announce Type: cross Abstract: This paper introduces tool efficiency, a new quantitative metric to evaluate the rate of useful tool calls in an LLM agent trajectory.
ToolSpace: Scaling Tool-Centric Environment Synthesis for Long-Horizon Agents
Large language models are deployed as long-horizon agents that compose diverse tools across MCP services into executable workflows. Existing MCP environment-scaling methods are data-centric: they firs...
ToolFailBench: Diagnosing Tool-Use Failures in LLM Agents
arXiv:2607. 04686v1 Announce Type: cross Abstract: Tool calling is central to modern language model agents, but aggregate benchmark scores often hide where tool use fails.
Growing One's AI Tools: A Paradigm of Practice-Grown Tools
The article describes how a conference interpreter, without programming training, built and iteratively improved a computer-assisted interpreting (CAI) tool over eight weeks, using version control and telemetry from 133 sessions and 20,000 utterances. The tool evolved through 62 commits and six versions, with a strategy change that reduced median end‑to‑end delay by more than a third within a single afternoon. The authors introduce the paradigm of practice‑grown tools, outlining its defining characteristics and proposing three propositions for assessing practitioners and their tools together.
Harness Engineering in LLM Tool Use via Agent-Native Reusable Tool Primitives
The paper introduces Tool Primitives, a design that replaces rigid API schemas with natural language interfaces for tool calling, enabling seamless inter-tool communication. It builds ToolFace, a repository of over 25,000 functions that LLMs can dynamically retrieve, and HEART, a harness engineering framework that orchestrates tool use with planning, routing, and verification. Experiments show HEART outperforms fine‑tuned models and leading commercial LLMs while cutting API costs by up to 85%.
ToolAtlas: Learning Once, Reusing Everywhere with Tool-Side Memory
arXiv:2607. 11126v1 Announce Type: new Abstract: Large language model (LLM) agents increasingly rely on external tools served by shared providers and accessed by heterogeneous downstream agents.
Open, Reliable, and Collective: A Community-Driven Framework for Tool-Using AI Agents
arXiv:2604. 00137v2 Announce Type: replace Abstract: Tool-integrated LLMs retrieve information, perform computations, and take real-world actions, but their reliability depends on both tool-use accuracy and intrinsic tool accuracy, including tool correctness, stability, and safety.
Controlling Tool Use with Heading-Specific Activation Steering
arXiv:2607. 05790v1 Announce Type: new Abstract: Tool-augmented large language models extend their capabilities beyond parametric knowledge through external tools, but tend to invoke them unnecessarily.
ToolLIFT: Lifting Tool-Specific Trajectories into Function-Level Graphs for Generalizable Tool Planning
arXiv:2608. 03468v1 Announce Type: new Abstract: Historical tool-use trajectories provide valuable experience for large language model (LLM) agents to plan and coordinate tool usage.
Rethinking the Role of Tool Graph Memory in Multi-Turn Tool Use
The paper investigates the effectiveness of tool graph memory—a component that records past tool transitions to guide future tool selection—in large language model agents performing multi‑turn tasks. Across nine models and two benchmarks, the authors find that tool graph memory rarely yields significant performance gains, often incurs more than twice the number of LLM calls, and its guidance is frequently incorrect. They observe that random or no guidance can achieve similar improvements, suggesting the benefits arise from additional computation rather than the memory itself, and that storing experiences as textual insights outperforms the graph approach with minimal extra calls.