cancel_task

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

With no annotations, the description fully covers cooperative cancellation, flag polling, status transition to 'cancelled', and Unreal Engine's lack of forced termination. Also notes idempotency behavior.

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?

Four sentences, each with distinct purpose: action, mechanism, limitations, and idempotency. No wasted words, front-loaded with core function.

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 simple single-parameter tool with no output schema, description covers all necessary behavioral aspects, edge cases, and limitations thoroughly.

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% for task_id, and description adds no extra information beyond the schema's description. Baseline 3 is appropriate.

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?

Clearly states it cancels a running task cooperatively. The verb 'cancel' and resource 'task' are explicit, and it distinguishes itself from sibling tools like list_tasks or poll_task by describing cancellation behavior.

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?

Provides explicit guidance on when to use (to cancel running tasks), when not to (workers that don't poll ignore cancellation), and idempotency for unknown/terminal tasks. No alternative tool mentioned, but context is sufficient.

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