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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real value beyond them: the financial consequence ("the whole reward goes back to your payout wallet") and the authentication requirement ("your own signed-in JWT"). It omits what happens to the task record afterward.

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 tight clauses, front-loaded with the action and immediately followed by the outcome and auth prerequisite. No filler or redundancy.

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 one-parameter destructive mutation with no output schema and no annotation for permissions, the description covers the effect, the refund behavior, and the auth requirement. The main gap is the missing task_id semantics, but overall it is close to sufficient.

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% for the single task_id parameter, so the description carries the burden. It only implies ownership via "YOUR open task," which is an authorization hint rather than format or value guidance. No syntax, source, or identifier details are provided.

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 (cancel) and resource (task) plus a scope qualifier (YOUR open task before anyone enters). An agent immediately understands the operation. It does not name or distinguish itself from siblings like task_submit or task_get, but the core purpose is unambiguous.

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?

"before anyone enters" gives a genuine timing precondition that implies when the tool is valid versus invalid. However, it names no alternative (e.g., what to do once someone has entered) and offers no explicit routing guidance among the many task_* siblings.

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