gemini 3.1 pro preview custom tools is the tool-calling-oriented release in Google's 3.1 Pro line — same reasoning core as the standard Pro preview, but positioned for agents that spend most of a conversation calling out to external functions rather than talking. If you're wiring up a multi-step agent that hits a database, a search API, and a code sandbox in sequence, this is the variant built with that loop in mind.
What "custom tools" changes
The underlying specs match Gemini 3.1 Pro Preview: a 1,048,576 token context window, up to 65,536 tokens of output, and full support for function calling, vision, and reasoning. What the naming signals is intent — this build is meant for agent frameworks and orchestration layers that define their own tool schemas and expect the model to reason across several tool calls in one turn, rather than for single-shot chat or document Q&A.
Pricing and how the context window plays into it
Input runs $2.00 per million tokens, output $12.00 per million, and cached input drops to $0.20 per million. That cached rate matters more here than in most Gemini tiers: a tool-calling agent typically resends the same system prompt, tool definitions, and conversation history on every step, and those are exactly the tokens caching discounts. A long-running agent session that would otherwise re-bill the same 5,000-token tool manifest on every step gets a 10x break on that portion once it's cached.
Where it fits next to the rest of the family
- Multi-step agent loops with several tool calls per turn
- Workflows built on custom function/tool schemas rather than a default toolset
- Tasks that need the reasoning depth of Pro, not the throughput pricing of Flash Lite
- Long sessions where cached system prompts and tool definitions offset the $2.00/$12.00 rate
Against Gemini 3.1 Flash Lite Preview's $0.25/$1.50 pricing, this model costs 8x more per token in both directions — pay it when the task genuinely needs Pro-level reasoning across tool calls, not for high-volume simple extraction.
The honest limitation
It's a preview build, so treat pricing and rate limits as subject to change before general availability. There's no published benchmark data attached to this release, so any claim about how it performs against other tool-calling models should come from your own eval on your own tool schema, not from a spec sheet.