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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the safety profile is covered. The description adds valuable context beyond that: cancellation is 'cooperative' (may not be immediate), it returns a Task status document, and whether the Territory Solution is unchanged or partially updated depends on the originating tool.

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 compact sentences, front-loaded with the core action and the fallback rationale. Each sentence carries meaning, though the final caveat is slightly vague.

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 needn't be spelled out, and the description still notes it returns the Task status document. It covers the cooperative nature and the downstream State caveat, leaving only the task_id semantics uncovered.

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?

Only one parameter (task_id) with 0% schema description coverage, yet the description does nothing to define it — no format, source, or how to obtain a task_id. Since the schema is bare, the description was the only place to compensate and it does not.

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+resource ('Requests cooperative cancellation of a task_id') and clarifies it is the fallback for clients lacking the native Tasks capability. It does not explicitly distinguish itself from siblings tasks_get and tasks_result, but the cancellation purpose is unmistakable.

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 'listed for clients without the Tasks capability' implies when this tool is relevant, but there is no explicit guidance on when to prefer tasks_cancel over tasks_get or tasks_result, nor any exclusions or prerequisites stated.

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