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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds important consequences: every decision records a receipt readable by downstream nodes, rejection cancels the run, and decisions are bound to revision/digest. It does not mention rate limits or auth beyond role, but adds enough beyond annotations.

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 concise sentences; the first front-loads the action and binding constraints, the second covers outcomes and permissions. Every clause earns its place with no redundancy.

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?

Given 7 parameters, nested objects, and no output schema, the description covers the core decision mechanics, outcomes, and permissions. It omits return value details (no output schema) and error codes beyond schema mention, but is largely complete for 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%, so the schema fully documents all parameters including nested objects and enums. The description mentions expected_revision and approval digest but does not add syntax or format details beyond the schema, so baseline 3 is appropriate.

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 states a specific verb ('Approve or reject') and resource ('manual quality gate currently pausing a workflow run'), and adds a distinguishing scope: bound to expected code revision and optional approval digest. It is clearly distinct from siblings like cancel_workflow_run or get_workflow_run.

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 describes the context of use (a paused manual gate) and authority ('Only the run owner or an organization admin may decide'), and implies the need for expected_revision. However, it does not explicitly name alternatives or when to use reject vs. cancel_workflow_run.

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