Claude Code Gemini MCP

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'deeply analyze' and 'perform reasoning and brainstorming', but doesn't describe what this entails operationally—e.g., whether it's a one-step process, if it involves iterative thinking, what the output format might be, or any limitations like token usage or time constraints. For a tool with no annotations, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Let Gemini-3-pro-preview deeply analyze complex problems') and adds key capabilities ('perform reasoning and brainstorming'). There's no wasted text, and every word earns its place in conveying the tool's intent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a tool for 'deep analysis' with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., structured reasoning steps, a summary), how it handles different thinking styles, or any behavioral traits. For a tool with 3 parameters and no structured output, more context is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters (problem, context, thinkingStyle) with clear descriptions and an enum for thinkingStyle. The description adds no additional meaning beyond what the schema provides, such as examples or nuanced usage of parameters. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'deeply analyze complex problems, perform reasoning and brainstorming' using 'Gemini-3-pro-preview'. It specifies the verb (analyze/reason/brainstorm) and resource (complex problems), but doesn't explicitly differentiate from sibling tools like gemini_brainstorm or gemini_query, which likely have overlapping functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings (gemini_brainstorm, gemini_query, gemini_review). It implies usage for 'complex problems' requiring 'deep analysis' but doesn't specify alternatives, exclusions, or prerequisites, leaving the agent to guess based on tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.