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

With no annotations provided, the description carries the behavioral burden. It discloses an important conditional behavior: cancellation is only possible before work has started. However, it does not mention what happens if the specialist has already started, whether cancellation is reversible, or what response can be expected.

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 sentence that states the action and the critical precondition without wasted words. The most important constraint is front-loaded and easy to parse.

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 single-parameter mutation tool, the purpose and precondition are present. However, with no annotations and no output schema, the description leaves out likely useful details such as error behavior when the task cannot be cancelled and whether the action is irreversible.

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%, and the description does not explicitly explain the task_id parameter. The meaning is weakly implied by 'Cancels the task,' but the description does not compensate for the lack of parameter documentation.

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 names a specific verb ('Cancels') and resource ('the task'), and includes the key precondition. It is clearly distinct from its siblings, which create, retrieve, or search tasks rather than cancel them.

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 supplies the relevant condition for use: cancellation is valid only when the specialist has not started work. It does not explicitly mention alternatives, but none of the siblings perform a comparable cancel operation, so this is sufficient.

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