cancel_task

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states that a cancelled task 'can no longer be resumed', disclosing irreversibility—a key behavioral trait for a cancellation operation. It does not cover other aspects like idempotency or permissions, but the primary consequence is clearly conveyed.

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 two short sentences, front-loaded with the verb 'Cancel', and every word earns its place. It conveys both the action and the critical consequence without any fluff.

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 cancellation tool with a single parameter and no output schema, the description covers the essential context: the action and irreversibility. It could mention return values or idle cases, but given the simplicity, it is reasonably complete and clearly distinguishes from continue_task.

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?

The description does not mention the task_id parameter at all, and schema description coverage is 0%, so the parameter semantics rest entirely on the property name. While task_id is self-explanatory and the schema specifies UUID format, the description fails to compensate for the low schema coverage.

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 states 'Cancel a task' with a specific verb and resource, clearly distinguishing this from sibling tools like get_task, continue_task, and delegate_task. The added clarification 'It can no longer be resumed' reinforces the terminal nature of the operation.

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?

Usage context is only implied: the description suggests this is the tool to use when a task must be terminated and cannot be continued later, which contrasts with continue_task. However, there is no explicit guidance on when to use this tool versus alternatives or whether there are prerequisites.

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