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

With no annotations, the description carries the behavioral disclosure burden and does well: it states that cancellation is cooperative, that the task state may remain unchanged or become partial, and that the return shape matches the native method. It does not cover permission requirements or error behavior, so it falls short of full transparency.

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 dense but front-loads the core purpose and usage rules, then adds prerequisite, return, and cancellation semantics. The internal tier and scenario labels add some noise, but the overall structure is efficient and appropriately sized for the tool.

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 one-parameter cancellation tool with no annotations and an existing output schema, the description covers purpose, usage conditions, prerequisite, return shape, and cooperative cancellation behavior. It is nearly complete, though it omits auth/error details that an agent might need in edge cases.

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 description coverage is 0%, so the description must add meaning for the sole task_id parameter. It does clarify that task_id comes from the immediately preceding async submission, which is useful, but it does not describe the ID format or any constraints beyond that origin.

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 identifies the tool as the tool-only equivalent of native tasks/cancel, which makes the cancel-task purpose clear from the name and text. It does not explicitly contrast with sibling tools such as tasks_get or tasks_result, but the operation is distinguishable from those by intent.

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?

It gives explicit when-to-use guidance ('Use only when this mirror appears in tools/list'), names the alternative for Tasks-capable clients (native tasks/cancel), and states the prerequisite that task_id must come from the immediately preceding async submission. This leaves little ambiguity about selecting or invoking the tool.

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