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 states the action ('review') but doesn't describe what the review entails (e.g., format of feedback, length, or any limitations like rate limits, authentication needs, or potential side effects). This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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: 'Let Gemini review code, architecture design, or technical solutions.' It is front-loaded with the core purpose and avoids unnecessary words, making it highly concise and well-structured.

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 review tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, output format, or any constraints. While the schema covers parameters well, the overall context for effective tool use is insufficient, especially for a tool that likely produces detailed feedback.

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?

The input schema has 100% description coverage, providing clear details for all parameters (content, reviewType, focus). The description doesn't add any semantic information beyond what's in the schema, such as examples or contextual usage tips. With high schema coverage, the baseline score of 3 is appropriate as the schema adequately documents the parameters.

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: 'Let Gemini review code, architecture design, or technical solutions.' It specifies the verb ('review') and the resources (code, architecture design, technical solutions). However, it doesn't explicitly differentiate from sibling tools like gemini_brainstorm, gemini_query, or gemini_think, which likely have different purposes (e.g., brainstorming ideas, answering queries, or analytical thinking).

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 alternatives. It doesn't mention sibling tools or other contexts, nor does it specify prerequisites or exclusions. Usage is implied by the purpose but lacks explicit instructions for selection among available options.

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