Google adds Tool Retrieval to the Gemini API to load tools on demand
The feature is in preview in the Interactions API and lets the model ask for a tool's schema only when it needs it.

When a smart assistant has many tools, each request gets heavy. Google now lets the assistant ask for each tool only when it needs it. The feature is in preview for programmers.
Hype check
The noise matches the real change.
Our editorial opinion, based on the sources below. How we score
Your call: hype or real?
Real = it will matter in daily use. Hype = louder than it is. One vote, and it can’t be changed.
Our view and readers’ views are opinions, not statements of fact about a product.
Why it matters
Developers building with dozens of tools can keep requests lighter without hosting their own index.
Watch: agents are learning to pick their own tools.
The details
- You add a tool_search tool and set defer_loading: true on the tools to hold back.
- The model sees each tool's name and description, but not its parameter schema until it asks.
- It works in the Interactions , in preview, with Gemini 3.6 and later, including all Gemini 4 models.
- No separate charge: bill at the model's rate, and the feature adds a small fixed block of input tokens.
- You can run the search in your own app instead of on Google's servers by setting execution to client, at one extra round trip per search.
Receipts
The company or lab said it. Primary source linked. Open the sources and check us.
Written with the help of AI tools and checked against the sources above. How we work
See a mistake? Tell us and we’ll fix it.