cancel_task

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

The annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description does not need to restate the safety profile. The description adds the 'running task' qualifier and the expected usage scenario, but it does not address what happens when the task is already completed or whether confirmation is required.

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?

Two short sentences with no filler: the first gives the action and object, the second provides a concrete use case. The information is front-loaded and 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?

The tool is simple, and the annotations plus the description give a solid starting point: cancel a running task by ID, notably for runaway reindexing or searches. However coverage lacks the optional confirm parameter's meaning and how cancellation behaves if the task is already done, which an agent may need to invoke it correctly.

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 only explains task_id indirectly by saying 'by id'; the confirm parameter is not described at all, leaving an agent uncertain about its role and whether it must be set.

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 a precise verb and resource: 'Cancel a running task by id.' It also differentiates from siblings by targeting running tasks, so an agent can distinguish it from get_task or stop-like operations.

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 description clearly says when to use it: 'for a runaway reindex or a search eating the cluster.' It does not explicitly mention when not to use it or name alternatives, but the use cases are concrete and helpful.

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