When a user asks an AI agent to do something that requires action — looking up an order, creating a ticket, scheduling a meeting — the model decides to call a tool. It emits a structured request (tool name, arguments), the agent runtime executes that request against the appropriate system, and the result is passed back to the model to continue reasoning.
Tool use is what separates an AI agent from a conversational text generator. Without it, the model can only talk about actions; with it, the model can actually take them. The quality of the tool surface — which tools exist, how they're described, how their outputs are shaped — heavily influences how well the agent performs.
In enterprise deployments, tool surfaces are typically exposed via an MCP server so the same tools can be consumed by multiple agents and model versions, and so governance controls can be applied consistently.