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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, and the description usefully adds that results include parity verdicts, model IDs, a score definition and an estimated cost delta, plus the default grouping behavior. It stops short of describing ordering, volume of results per deployment, or how status values are computed.

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?

Two sentences plus a short question list, front-loaded with the core capability before the view-mode detail. The question examples are slightly redundant with the opening sentence but still earn their place as routing cues; overall tight with no filler.

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?

With no output schema, the description correctly compensates by naming the payload contents (parity verdicts, model IDs, score definition, cost delta) and the default grouping. Pagination via cursor and the limit default live in the schema, but guidance on result ordering and how the eleven status values relate to the verdicts is left unstated.

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%, so every parameter including repo, view, limit, cursor and both enums is already documented in the schema. The description only restates the view='pr' grouping and the per-agent default, adding no syntax or behavioral detail beyond what the schema provides, so the baseline of 3 applies.

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?

Names a specific capability — verifying whether deployed fixes/model swaps worked in production — and enumerates the concrete artifacts returned (parity verdicts, model IDs, score definition, cost delta). It also distinguishes its two operating modes (per-agent default vs. PR-grouped), which lets an agent separate it from nearby siblings like get_pr_context and get_verification_evidence.

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 three quoted questions ('did my fixes work?', 'what PR changed this?', 'show me PR impact') give clear invocation contexts tied to the two view modes. However, it never names an alternative tool or states when NOT to use it, so an agent comparing it against get_pr_context or get_production_test must infer the boundary itself.

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