cancel_user_request

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

With no annotations, the description carries the full behavioral burden. It does disclose an important permission limit ('Only the creator can cancel') and the auth path, which adds context beyond the schema. However, it does not describe side effects, whether cancellation is reversible, or what happens to the request afterward.

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 with the core action. The access note is somewhat long but provides necessary auth context for an agent. No redundant or filler content.

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 one-parameter cancellation tool, the description covers the main action, creator restriction, and access requirements. But it lacks any guidance on distinguishing this from the closely related cancel_verification_request, and it does not mention expected return behavior or post-cancellation state.

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 schema already provides full coverage for the single parameter: 'Verification request ID to cancel' with 100% coverage. The description adds no additional meaning about the id format, required state, or how to obtain it, so it does not improve on the schema.

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 clear action and object: 'Cancel a pending verification request.' It is specific enough about the operation. However, it does not distinguish this tool from the similarly named sibling cancel_verification_request, so some ambiguity remains.

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 gives access prerequisites ('needs a Proof account', API key setup or login) and a constraint ('Only the creator can cancel'), but it provides no guidance on when to use this tool versus alternatives like cancel_verification_request, nor any exclusions based on request state or ownership verification.

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