pdf_signer.cancel

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

With no annotations, the description carries the full burden, and it does disclose the post-condition (document returns to 'open' and becomes editable again), which is genuinely useful. However, it omits auth/permission needs, whether signers are notified, and whether cancellation is reversible.

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?

One compact sentence that front-loads the action and follows with the state transition. No filler, though the parenthetical caller note slightly interrupts the main clause.

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 described, but for a mutation-style tool with no annotations and 0% param coverage, the definition leaves auth requirements, side effects, and parameter meaning unaddressed.

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 0% and the description mentions no parameters at all. Both doc_id (required) and user_id (optional, default '') are left undocumented, so the definition fails to compensate for the coverage gap.

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 the signing ceremony') and adds the resulting state ('document returns to open'). This distinguishes it from pdf_signer.sign, but no sibling is named explicitly, so an agent must still infer the boundary from the pdf_signer.* prefix.

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 phrase 'called by the signing app' implies the caller context but gives no explicit when-to-use/when-not guidance or alternatives (e.g., how it differs from pdf_edit or pdf_request_signature). Usage is implied rather than instructed.

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