Cancel a task that has not started

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond them by specifying the exact state transition (Draft -> Voided) and its effect (the task will never run), which clarifies what 'destructive' means here.

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?

One front-loaded sentence with no filler; the state change and its consequence arrive immediately.

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 low-complexity, single-parameter mutation with no output schema, the description covers the action and effect adequately. It omits the failure mode for tasks that have already started, which the title implies but the description body never states.

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% and the single required parameter task_id is never mentioned in the description. With only one parameter the burden is light, but the definition gives no hint about how a task is identified (ID format, source, etc.).

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 and resource ('Marks a Draft task as Voided') plus the state transition and consequence ('so it never runs'). That is enough to distinguish it from create_task/get_task/list_tasks, though it never names a sibling 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?

The title and the phrase 'a Draft task' imply the precondition that only unstarted tasks can be cancelled, which is useful routing context. However, the description never states when to prefer this over alternatives or what to do for a task already running.

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