Review Verdict

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful context by revealing that the tool composes three sub-tools and returns a unified verdict plus a confidence score. It does not go into depth about possible latency or failure modes when invoking the full pipeline, but that is not a major gap for a read-only aggregator.

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?

Three sentences with zero filler: the first states the composite action and output, the second gives the primary use case, and the third lists alternatives. The information is front-loaded and each sentence earns its place.

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?

For a composite tool with 9 parameters and no output schema, the description covers the essential decision of when to use it and what it returns. It could say more about the structure of the 'unified verdict' or the fact that the PR selector switches mode between GitHub and local, but the schema already documents those details, so the description is reasonably complete.

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 input schema already documents all 9 parameters in detail. The description does not add parameter-level semantics beyond mentioning the high-level pipeline, which meets the baseline for a fully documented schema.

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 names a specific composite operation—'Run the full review pipeline in one shot: change_impact plus review_context plus review_gate'—and clearly states the unique output: a unified verdict with a derived confidence score. This differentiates it from its siblings, which each provide only part of the picture.

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?

It explicitly states when to use this tool ('when you want the complete picture of a change in a single call') and names alternatives: review_context for diff metadata only and review_gate for the gate verdict alone. This gives the agent direct routing guidance.

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