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

With no annotations, the description carries the disclosure burden. It does reveal that cancellation is scoped to the caller's own OPEN task and that a full escrow refund occurs, which is useful. However, it does not state whether cancellation is irreversible, how the refund is returned, or what happens if the task is not OPEN.

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 a single, front-loaded sentence that communicates scope, eligibility, and financial consequence without wasted words. It is ideal for quick agent comprehension.

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?

This is a simple one-parameter tool with no output schema, and the description covers the essential context: what can be canceled, who can cancel it, the required status, and the refund effect. It could mention failure modes or finality, but the core contract is complete enough.

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 100%, and the only parameter task_id already has a clear example. The description adds no parameter-specific detail, so it earns the baseline score for high schema coverage.

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 uses a specific verb ('Cancel') and a precise resource ('your own OPEN task'), and adds the consequence of a full escrow refund. This clearly distinguishes cancel_task from siblings like claim_task, deliver_task, and approve_task.

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 phrase 'your own OPEN task' states the key precondition and target population for this tool, so an agent knows when it is appropriate. It does not explicitly name alternatives or list when-not-to-use conditions beyond the OPEN status, but the context is sufficient.

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