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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation risk is covered. The description adds context the annotations do not: the outcome is mode-dependent, and a request may not take effect immediately because it can require refund processing or operator intervention. It still omits idempotency and what the response confirms, so it is good rather than exhaustive.

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 front-loaded sentence that pairs each action mode with its condition, with no filler or restatement of the name. 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 destructive no-output-schema tool, the description usefully flags that the outcome can be asynchronous and involve refunds or operators, which is more than the annotations convey. However, it does not describe what the caller gets back (confirmation vs. pending state) or the meaning of reason, and no output schema exists to fill that gap.

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 all three parameters, so the description carries the full burden but says nothing about job_id, job_token, or reason. job_id and job_token are inferable from their names, but a token requirement and a 2000-char reason field are left unexplained. This is a clear gap against the low-coverage baseline.

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 (HumanEndpoint job), and usefully splits the action into two modes: immediate cancellation for unpaid jobs vs. a cancellation request for work already underway. The name/title already imply cancellation, but the description adds the important scope distinction of unpaid vs. in-progress. It does not explicitly contrast with siblings, though cancel is self-evidently distinct from create/get/list/reply.

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 gives the selecting condition between the two modes: unpaid work is cancelled immediately, while work already underway becomes a request that may require refund or operator handling. That is genuine when-to-use guidance. It stops short of stating when not to use the tool or naming alternatives (e.g., using reply_to_job instead).

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