task_cancel

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

No annotations are provided, so the description fully carries the burden. It states the tool cancels tasks, implies destructive action, and scopes it to the user's in-progress tasks. It mentions a confirmation dict in return but does not detail irreversibility or side effects, which is acceptable for a cancellation action.

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 well-structured with a summary line, bullet points, and examples. It is front-loaded with the main action. Some minor redundancy (e.g., 'Dict with cancellation confirmation') could be trimmed, but overall efficient.

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 that an output schema exists (not shown but indicated in context), the description need not explain return values. It covers input, exceptions, and examples thoroughly. No gaps remain for a cancellation tool.

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 compensate. It thoroughly explains both parameters: task_id (UUID string, optional if all=True) and all (boolean). It adds the context that at least one must be provided, with examples showing exact usage patterns.

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 that the tool cancels running or queued tasks, distinguishing between canceling by ID or all tasks. It uses the specific verb 'cancel' on the 'task' resource and differentiates from sibling tools like task_list, task_show, task_wait, and task_event_list.

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 provides when to use each parameter: either provide task_id or set all=True. Includes a ValueError condition if neither is provided, and gives two clear examples demonstrating both use cases.

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