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

With no annotations, the description carries the full burden. It discloses the key behavioral constraint of only-pending eligibility and the authentication gate, going beyond a mere restatement of the tool name. It does not describe side effects, irreversibility, or error behavior for non-pending requests, but for this simple cancellation action the disclosed traits are reasonably sufficient.

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 compact and front-loaded: the main action and constraint appear in the first sentence, followed by a concise ACCESS note. There is no fluff or redundant restatement of the tool name.

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 single-parameter mutation tool with no output schema, the description covers the essential operational context: what it does, when it applies, and the authentication prerequisite. It could be slightly more complete by explicitly distinguishing itself from cancel_user_request, but the name and pending-request wording already reduce confusion.

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?

The single parameter 'id' is already fully described in the input schema as 'Verification request ID' (100% schema description coverage). The tool description adds no extra meaning or context to the parameter, so the baseline score of 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 uses a specific verb 'Cancel' with the resource 'verification request' and constrains it to 'pending' requests. This clearly differentiates it from sibling tools like cancel_user_request and create_verification_request without requiring the reader to open the schema.

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 the precondition that only pending requests can be cancelled and provides an authentication requirement with a concrete instruction to re-call after authenticating. However, it does not explicitly mention alternatives such as cancel_user_request or explain when not to use this tool.

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