Source: blog.google/innovation-and-ai/technology/developers-tools/gemini-api-tool-retrieval
Tool Retrieval lets an agent keep its full tool library on standby. Developers add a tool_search tool to a request and set defer_loading to true on the tools to hold back. The model still sees each deferred tool's name and description, but the parameter schemas stay out of context until the model asks for a tool by name.
When that happens, the API loads the full schema and the model emits the function call within the same request. Each step appears in the interaction's steps list, which makes it easier to check which tools the model considered. Gemini runs the search on the server, so there is no index to build or host.
Developers who maintain their own tool registry can instead declare tool_search with execution set to client and run the lookup in their own app, which adds one round trip per search. Remote MCP servers are also supported: setting defer_loading on an mcp_server tool loads each exposed tool on demand. Tool Retrieval has no separate charge, and it works with Gemini 3.6 and later models, including Gemini 4 models.
Why it matters if you build agents
Agents with dozens or hundreds of tools can keep frequently used tools loaded up front and defer the rest, which may cut input tokens and latency.
Savings depend on usage: each schema the model loads is billed as input for the rest of the conversation, so developers should measure the effect on their own traffic.
Because deferred schemas stay out of the start of the prompt, prefix caching should remain effective across turns.
Get stories like this every weekday
One short email with the day's agent tooling news.