Tool use is the capability that lets AI agents interact with external systems — send emails, query databases, browse the web, control applications. Without tool use, agents can only generate text; with tool use, they can take real actions. It's the foundation that makes agents useful.
What tool use is
Tool use (also called function calling) is the agent's ability to call external functions — pieces of software that do things. An agent with email tools can send emails. An agent with browser tools can navigate web pages. An agent with file system tools can read and write files.
The agent decides which tool to use and what arguments to pass, based on the user's request. The surrounding software executes the tool call and returns the result to the agent, which can then decide what to do next.
Types of tools
Modern agents have access to many types of tools:
- Web browsing tools. Navigate URLs, extract page content, click elements, fill forms. Used by browser agents like Operator and Mariner.
- API tools. Call external APIs — Gmail, Slack, HubSpot, Salesforce, Stripe. Most business agents are API-tool orchestrators.
- File system tools. Read, write, and modify files. Used by coding agents like Cursor and Claude Code.
- Code execution tools. Run Python, JavaScript, shell commands. Lets agents do anything a programmer can do.
- Desktop control tools. Move the mouse, click, type, take screenshots. Used by desktop agents like Claude Computer Use.
- Database tools. Query SQL databases, search vector databases.
- Communication tools. Send emails, post to Slack, send SMS.
How tool use works
Tool use involves a loop:
- The agent receives a user request
- The agent decides which tool to use and what arguments to pass
- The surrounding software executes the tool call
- The result is returned to the agent
- The agent decides whether to call another tool, respond to the user, or ask for clarification
This loop — decide, call, execute, observe — is the agentic loop that defines AI agents. Tool use is what makes the loop productive.
Why tool use matters
Tool use is what transforms LLMs from text generators into agents. Without tools, an LLM can only talk about the world. With tools, it can act on the world. Three specific benefits:
- Real-world actions. Sending emails, making purchases, updating databases — anything software can do, an agent with the right tools can do.
- Real-time data. Tools let agents access current information — weather, stock prices, inventory levels — rather than relying on stale training data.
- Multi-step workflows. By chaining tool calls, agents can complete complex tasks that no single tool could handle.
Tool use vs MCP
Tool use and MCP (Model Context Protocol) are related but distinct:
- Tool use is the capability — the agent's ability to call external functions.
- MCP is a protocol — a standard way for tools to be exposed to agents.
In practice, MCP makes tool use more portable. Build an MCP server for your tool once, and any MCP-compatible agent can use it. Without MCP, you'd need to build separate integrations for each agent platform.
Limitations of tool use
Tool use is powerful but has limitations:
- Agents can only use tools they have. If a tool isn't available, the agent can't use it. Agents are limited by their tool set.
- Tool calls can fail. APIs go down, permissions are denied, arguments are invalid. Good agents handle failures gracefully.
- Agents sometimes pick the wrong tool. Modern models are good at this but not perfect. Similar-looking tools can confuse them.
- Arguments can be wrong. Even with the right tool, the agent might pass incorrect arguments.
These limitations are why human-in-the-loop matters for high-stakes tool use. Tools amplify both the upside and downside of agent capabilities.
Explore more AI agent guides
Browse our complete library of reviews, comparisons, and how-to guides.
Browse all guides