turbosign_void

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

With no annotations, the description fully bears the responsibility. It discloses critical behavioral aspects: the reason is recorded in the audit trail, is required, and the action is irreversible. This provides important context beyond a simple 'cancel' and alerts the agent to potential consequences.

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?

Two concise sentences with no filler. The first sentence states the action and condition; the second conveys key consequences and an alternative. Information is front-loaded and 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?

For a tool with only two simple parameters and an output schema, the description covers the purpose, the condition, the required reason, audit trail recording, irreversibility, and a restart path. This is sufficient context for an agent to select and invoke the tool correctly.

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 has 0% description coverage, so the description must add meaning. It explicitly states that reason is required and recorded in the audit trail, clarifying why that parameter is needed. document_id is self-explanatory as the target request, so overall the description compensates well for the schema's lack of detail.

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' and a clear resource 'a signature request that has not completed,' which distinguishes it from sibling tools like turbosign_resend or turbosign_send. The condition 'has not completed' further clarifies the scope.

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 implies when to use the tool: only for signature requests that have not completed. It also gives an alternative action ('send the document again') if the user needs to restart. However, it does not explicitly name sibling tools as alternatives or state when not to use it, leaving a minor gap.

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