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

Annotations declare the mutation profile (destructiveHint=true, idempotentHint=false), so the description only needs to add what they don't cover. It does: 'Does not issue refunds' is a real financial consequence an agent cannot derive from annotations, and 'unclaimed' is a state precondition. It stops short of saying what happens if the task is already claimed.

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 sentences, no filler, with the actor and state constraint front-loaded before the financial caveat. Every clause 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?

For a two-parameter, no-output-schema mutation tool this covers actor, state precondition, and the refund consequence. A note on the failure mode when the task is not unclaimed would make it fully complete.

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 coverage is 100% and the actorId description already routes the agent to list_my_actors, so the schema carries both parameters fully. The description adds no parameter-level meaning, which matches the baseline 3 when the schema does the heavy lifting.

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 (cancels) and resource (task), plus two qualifiers that sharpen it: the caller role ('Requester') and the required task state ('unclaimed'). This separates it from neighbors like withdraw_offer or submit_task, though it does not name a sibling explicitly.

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 precondition 'unclaimed' implicitly tells the agent when this is available, but there is no explicit when-not guidance or pointer to an alternative (e.g., what to do for a task that has already been claimed). Usage is inferable, not stated.

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