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

Annotations already indicate destructive and idempotent behavior. The description adds valuable nuance: credits are refunded only for videos not started, and already-fetched content remains paid for and remains in results. It also states calling it is 'Free', which clarifies cost implications beyond the refund note.

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?

The description is short and efficient: it states the core action first, then the key refund caveat, then the free-to-cancel fact. Every sentence earns its place and there is no 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?

For a one-parameter destructive action, the description covers the essential behavioral nuance (refund policy), annotations cover idempotency and destructiveness, and an output schema is already available. The only minor gap is not explicitly describing what happens to the job itself after cancellation, though it is largely inferable.

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?

The only parameter, `job_id`, is fully documented in the JSON schema with its source (`id returned by submit_transcripts_job`). The description adds no additional parameter-level guidance, which is acceptable because schema coverage is 100%.

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 clearly states the verb-action ('Cancel') and resource ('a batch job'), and ties cancellation to a specific `job_id` from `submit_transcripts_job`. It distinguishes this tool from all sibling read/query tools without ambiguity.

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 explains the result of canceling and the credit refund condition, but it does not explicitly state when to use this tool versus alternatives, such as checking job status with get_transcripts_job or allowing the job to continue. The right usage is implied by the action name, not spelled out.

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