cancel_task

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: cancellation blocks on backend cleanup and repeat calls are safe. It does not state what happens to the task's result, whether the task must be in a particular state, what errors occur for unknown task IDs, or any authorization requirements.

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?

A single efficient sentence with no filler, and the core action is front-loaded before the safety note. Given this tool has no annotations and an undocumented parameter, however, it is arguably too terse.

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 one-parameter cancellation tool, the description covers the action, the blocking cleanup, and idempotency. It is still incomplete regarding post-cancel task state, error behavior, and the origin of task_id, and no annotations or output schema exist to fill those gaps.

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 0%, and the description says nothing about task_id beyond the name. Even though task_id is fairly self-explanatory, the description does not say where to obtain it (e.g., from submit_task) or whether it must be a currently active task.

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: "Stop the delegated task." An agent can distinguish this from siblings like get_result, wait_task, or discard_task_changes, but the description does not explicitly name or contrast with any alternative.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. "Repeated cancellation is safe" hints at idempotent usage but does not tell the agent whether to cancel versus wait or fetch results, nor whether the task must be running first.

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