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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description goes beyond that by disclosing the escrow refund outcome and the API-key authentication requirement, neither of which appears in the structured fields. It still omits what happens on a failed/duplicate cancellation, which is why it is not a 5.

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, front-loaded sentences: the action and its consequence come first, followed by the auth prerequisite. Nothing is wasted, though the extreme brevity for a destructive operation borders on under-specification rather than tightness.

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 low-complexity destructive tool with one parameter and no output schema, the description covers the core action, its refund consequence, and the auth requirement. It is still silent on failure modes (e.g., cancelling an already-claimed task) and on repeat-call behavior, which matters given idempotentHint=false.

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 single required parameter (task_id) is undocumented in both schema and description. The parameter name is largely self-explanatory and the tool takes only one argument, so the gap is minor, but the description does not compensate for the missing 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?

States a specific verb and resource ('Cancels an open task') plus a concrete side effect ('refunds the escrow'), which the title reinforces with the 'unclaimed (poster)' qualifier. It does not explicitly differentiate itself from siblings such as dispute_task or reject_task, so it falls short of a 5.

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 'open task' implies the precondition (only unclaimed/open tasks can be cancelled), giving implied usage guidance, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., dispute_task for claimed tasks). An agent must infer the boundary from the title.

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