cancel_task

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

Discloses the key behavioral precondition (queue vs running) and suggests alternative. No annotations provided, so description carries full burden. Missing details on side effects or error handling, but adequate for a cancel operation.

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, front-loaded with critical information, no fluff. Every word earns its place.

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?

Given one parameter, no output schema, and sibling tools, the description covers the essential context: when to use, when not, and alternative. No missing critical information.

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 coverage is 100% and the description does not add extra meaning beyond the schema's description of 'tasktoken'. Baseline 3 is appropriate as the description adds no new semantic information.

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?

Description clearly states the tool cancels a task in the queue before worker assignment, using specific verb 'Cancel' and resource 'task that is still in the queue'. It distinguishes from sibling tool 'kill_task' for running tasks.

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 states when to use (tasks in queue) and when not (running tasks), and provides the alternative tool name 'kill_task'. This is excellent guidance for agent decision-making.

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