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

Annotations already flag this as destructive, non-read-only and idempotent, so the safety profile is covered. The description adds real value beyond them: the signing link stops working (external side effect for the recipient) and the cancel does not refund the monthly count (an irreversible quota consequence). It still doesn't say what happens to the request record or how it errors on an already-signed request, so not a 5.

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?

Three short sentences, front-loaded with the action and eligibility, then the two consequences. Every sentence carries distinct information with zero 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?

No output schema exists, so the description carries return/behavior burden, and it does cover the key consequences an agent needs before calling. It is near-complete for a 2-param destructive tool, missing only the request_id semantics and post-cancel record 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?

Schema description coverage is only 50%: request_token is documented in the schema, but request_id carries no description anywhere. The description adds no parameter meaning at all, so it fails to compensate for the undocumented identifier.

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?

Specific verb (cancel) plus resource (signature request) plus a precondition ("not signed yet") that no sibling tool covers — send_for_signature, get_signature_status, download_signed_pdf and find_signature_requests are all clearly distinct operations. An agent picking among the six siblings can select this one without opening a 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?

The description gives a clear eligibility condition ("a request that is not signed yet"), which implicitly excludes already-signed requests. It stops short of naming the alternative action for signed requests or explicitly stating when not to use it, so it is clear context without exclusions.

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