cancel_task

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Cancel a task' implying a state change but does not describe reversibility, side effects (e.g., what happens to subtasks without force), permissions required, or response format. The mention of force=True hints at behavior with subtasks but is insufficient for a mutation 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?

The description is extremely concise with two short sentences. It is front-loaded and contains no extraneous information. 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 the lack of annotations and output schema usage (not mentioned), the description is incomplete. It does not explain return values, prerequisites, or behavior under various conditions (e.g., cancelling a task with open subtasks without force). For a tool with siblings and parameters, more context is needed.

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 input schema has 0% description coverage, so the description must compensate. It explains the force parameter ('use force=True to cancel all open subtasks'), which adds meaning beyond the schema (boolean with default). However, the required task_ref parameter is not explained, and the description does not elaborate on its format or constraints.

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 clearly states the action (cancel) and the resource (task). It includes a specific parameter detail (force for subtasks) that adds clarity. Although it doesn't explicitly differentiate from siblings like finish_task or reset_task, the purpose is unambiguous.

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 only usage guidance is about the force parameter ('Use force=True to cancel all open subtasks'). There is no guidance on when to use cancel_task versus sibling tools (e.g., finish_task, reset_task), nor are there any exclusions or prerequisites mentioned.

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