gemini_review

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 indicates it uses Gemini Pro, which implies external service calls, but doesn't mention side effects, data privacy, retry behavior, or what the output looks like. The absence of read-only hints or side-effect disclosures 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 extremely concise: two short sentences. It front-loads the core purpose and provides a brief usage context. Every word is meaningful, with no fluff.

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?

There is no output schema and no annotations, so the description must compensate. It fails to explain what the review returns, how to interpret results, or any potential side effects. With 4 parameters and a complex task, this is incomplete for reliable tool 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 coverage is 100% and each parameter has a description, so the baseline is 3. The tool description adds no extra parameter semantics beyond what's already in the schema, but the schema itself is adequate. 'code' is clearly the focus from the required field and the tool's purpose.

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 reviews code quality using Gemini Pro, which is a specific verb + resource. It also mentions cross-validation independent of Claude, giving context. However, it doesn't distinguish itself from the sibling 'gemini_critique', so it's slightly short of full differentiation.

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 implies a use case: cross-validation independent of Claude. This gives some context on when to use the tool, but it doesn't explicitly state when not to use it or provide alternatives like gemini_critique. There's no clear comparative guidance.

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