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

Annotations already cover the key traits: readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds the important nuance that this is a request, implying cancellation may not be immediate or guaranteed, and that only authorized jobs can be cancelled. It stops short of stating what happens to in-flight jobs or partial results, so it adds value but not rich behavioral context.

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 stating the action and scope. Every word earns its place with no redundancy or filler.

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?

An output schema exists, so return values need not be explained. Annotations and the full schema cover the structured details. The only remaining gap is the absence of prerequisite or post-call guidance, but the definition is largely complete for a single-purpose cancellation tool.

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 100% and the anyOf variants fully document job_id, product, schema_version, and idempotency_key constraints. The description adds no further parameter meaning beyond what the schema already provides, which fits the baseline 3 when structured data 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?

The description states a specific verb (Request cancellation) and resource (product job). It uses 'one authorized product job' to scope it, which differentiates from submission siblings like submit_quantum_job and run_buyer_job, though it doesn't name the primary alternative 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?

Usage is implied: request cancellation for one authorized product job. There is no explicit when-to-use guidance or mention of alternatives such as checking status first with get_job_status, nor any warning about jobs already completed. Adequate but with clear gaps.

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