Cancel async task

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

Annotations indicate destructive mutation (readOnlyHint=false, destructiveHint=true). Description adds specific context on cancellation conditions and supported tasks. No contradictions.

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 sentences with no waste. First sentence states primary action, second provides necessary constraints. 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 simple cancel operation with one parameter and no output schema, the description covers all necessary behavioral details, including restrictions and supported task types.

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 describes the single parameter 'id' with full coverage. Description adds no extra parameter details beyond what schema provides. Baseline score of 3 applies.

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?

Clearly states the tool cancels a queued async task, specifies supported task types (Seedance video tasks) and states. Distinguishes from siblings as no other cancel tool exists.

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?

Explicitly describes when to use (queued tasks with cancellation support) and when not (already processing, completed, failed, expired, unsupported). Provides concrete examples of supported task IDs.

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