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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that cancellation may be immediate or may route to operator/refund handling, which is meaningful. However, it omits irreversibility, authorization requirements, and what happens to an in-flight job, leaving real gaps for a mutation tool.

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 sentence that front-loads the primary action and then the conditional mode. No wasted words, though the terse phrasing packs two behaviors into one clause without structure that would help an agent branch cleanly.

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 mutation tool with no annotations, no output schema, and 0% parameter coverage, the description explains the behavioral fork but says nothing about parameters, auth, or the result of each path. It is minimally viable but leaves important gaps an agent needs before invoking.

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 three parameters (job_id, reason, job_token), and the description mentions none of them. It never clarifies that reason is optional free text up to 2000 chars, nor why a job_token is required alongside job_id, so it fails to compensate for the documentation gap.

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/request cancellation) on a specific resource (job) and distinguishes two modes: immediate cancellation for unpaid work versus a request path for work needing refund/operator handling. It does not name or differentiate itself from siblings like human_get_job or human_reply_to_job, 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?

Provides an explicit selection rule between the two modes based on payment state: 'unpaid job immediately' versus 'work that may require refund/operator handling.' That is actionable conditional guidance, though it offers no exclusions or prerequisites (e.g. who may cancel, what states are eligible).

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