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

With no annotations, the description carries full burden. It reveals that this is a mutation (cancel) with a precondition, but does not describe side effects, reversibility, required permissions, error behavior (e.g., if already finished), or what the response contains.

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 a single sentence of nine words with zero waste, and the key operation and precondition are front-loaded.

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 mutation tool with no annotations and no output schema, the description is too sparse. It omits critical invocation details such as what happens on success/failure, whether the operation is idempotent, and how to handle already-finished runs.

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 single required parameter run_id has 0% schema description coverage, yet the description provides no additional meaning about what run_id refers to (e.g., a run identifier from handoff_task or get_run) or its expected format. The schema's UUID format is the only clue.

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 specific verb ('cancel') and resource ('handoff') plus a precondition ('has not finished'). It implicitly distinguishes from siblings like get_run (read) and handoff_task (initiate), though it does not name alternatives explicitly.

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?

Usage is implied by the precondition 'has not finished', suggesting it applies only to active handoffs. However, there is no explicit guidance on when to use this versus get_run to check status, or what to do if the handoff is already finished.

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