What changed
Google added Tool Retrieval to the Gemini Interactions API so an agent can see tool names and descriptions while loading full parameter schemas only when needed. Server-side retrieval can cover declared functions or remote MCP servers, while client-side retrieval can query a private registry or permission filter.
Why it matters
Large tool catalogs consume context and weaken selection, but deferred loading also moves schema discovery and permission filtering into a new runtime boundary that must be observable and deny-safe.
What to do
Canary fifty representative tools, defer the long tail, and compare selection accuracy, input tokens, latency and denied-tool behavior against the current full-schema baseline; inspect every tool-search step before enabling writes.
Caveat
The feature is preview and Google supplies the efficiency rationale, not independent production results. Client-side retrieval adds a round trip, and loaded schemas remain billable input for the rest of the conversation.