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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: approving a proposal applies its edits, and apply/drop leave the review open, which tells the agent what state results from each action.

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 tight sentences with no filler, and the core purpose is front-loaded before the action semantics. Minor ambiguity from the unexplained 'CHECK' term keeps it from a 5.

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?

An output schema exists, so return values need no explanation, and annotations cover the destructive/idempotency profile. Still, for an 8-param mutation with 38% schema coverage, the description leaves action 'decline' and all concurrency/identity params unaddressed, and mentions a 'CHECK' action not present in the enum.

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?

Coverage is low (38%) across 8 params, so the description should carry more weight. It does clarify the effect of approve/apply/drop on changeIds, but it omits decline entirely and says nothing about expectedRevision, expectedVersion, editorKey, or decisionId, leaving real gaps relative to the coverage shortfall.

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?

States a specific verb (records) and resource (decision on a pending review), which is clearly distinguishable from siblings like document.compare_decide and document.view_ack. It does not, however, explicitly contrast itself with the other decide-style siblings.

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 explains the consequence of each choice (approve applies edits, apply/drop leave the review open), which implies when to pick each action. But it never states when to use this tool versus alternatives such as document.compare_decide or document.view_ack, and no preconditions are given.

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