Claude Code Gemini MCP

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the tool sends queries but doesn't disclose rate limits, authentication needs, response format, error conditions, or whether it's idempotent. For a model interaction tool, this leaves critical operational details unspecified.

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 immediately conveys the core function. Every word earns its place with no redundancy or unnecessary elaboration, making it easy to parse and understand at a glance.

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 this is a model query tool with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of response to expect, potential limitations (e.g., token limits), or how it differs from sibling tools. The agent lacks critical context for effective tool selection and invocation.

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 fully documents all three parameters. The description adds no parameter-specific information beyond implying 'prompt' is the main input. This meets the baseline for high schema coverage but doesn't enhance understanding of parameter relationships or usage patterns.

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 action ('Send any query') and target resource ('Gemini-3-pro-preview model'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings (gemini_brainstorm, gemini_review, gemini_think), which likely also interact with Gemini models but for more specific purposes.

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. It doesn't specify if this is for general-purpose queries while siblings are for specialized tasks, or if there are any prerequisites or constraints. The agent must infer usage from tool names alone.

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