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

The readOnlyHint=true and destructiveHint=false annotations already establish the safety profile. The description adds useful behavioral context by saying it returns a comprehensive set of review evidence in one call and lists the categories of information included. It does not contradict annotations and adds meaningful value beyond them.

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 front-loaded with the core purpose and then supports it with a return-content list and example questions. The long enumeration of returned items is justified by the absence of an output schema, though it is somewhat list-heavy rather than maximally tight.

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 read-only getter with no output schema, the description does a good job of explaining the rich content returned and the review scenarios it supports. It does not cover pagination, limits, or relationships to alternative tools, leaving a few minor gaps.

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 deploymentId, customerId, and includeDiff with clear descriptions. The tool description adds no parameter-specific meaning beyond what the schema provides. 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 it provides a comprehensive reviewer briefing for a specific deployment/PR and enumerates the content returned. It does not explicitly name or differentiate itself from similar siblings such as get_review_case or get_verification_evidence, so it is clear but not sibling-differentiating.

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 concrete usage signals via example user intents: 'tell me about this PR', 'should I merge this?', 'what does this fix?'. It establishes when to reach for this tool, but gives no explicit when-not-to-use guidance or alternative tool recommendations.

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