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

With no annotations, the description carries the full behavioral burden. It usefully discloses two effects: links stop working and already-signed documents remain signed. However, it does not state authorization requirements, what happens to non-open or already-completed requests, or any reversibility constraints beyond the signed-document note.

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 with no waste. The cancellation action is front-loaded, followed by the two key consequences, making the description easy to scan.

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 not be explained. For a simple mutation tool, the description covers the core effect but leaves out authorization requirements and edge-case behavior such as attempting to cancel an already-signed request. It is adequate but with clear gaps.

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 0%, so the description should compensate for the undocumented signature_request_id parameter. It never mentions the parameter, its format, or where to obtain it. The parameter is simple and self-evident from its name, but the description still fails to add meaning beyond 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?

States a specific verb and resource: cancel an open signature request. The scope word "open" narrows the action usefully, and the action is distinct from signatures_get, signatures_list, signatures_newLink, and signatures_request. It does not explicitly name or differentiate against those siblings, which keeps it below a 5.

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?

"Open signature request" implies the applicable condition for use, but the description offers no explicit when-not guidance, prerequisites, or alternatives. Usage must be inferred from the verb and scope rather than being spelled out.

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