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

The annotations already declare this as destructive, non-read-only, and idempotent. The description adds useful behavioral context beyond those annotations: a running band task finishes, charging only occurs on success, and the caller should read status until stopped.

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 front-loaded with the main action and keeps each sentence focused on operational guidance. It is somewhat dense, but the correction workflow and billing caveat are useful rather than redundant.

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?

Given the destructive annotation and the lack of an output schema, the description provides enough context about cancellation scope, status polling, follow-up transcription, and billing behavior. The main remaining gap is the undocumented job_id parameter.

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%, and the only parameter, job_id, has no description in the schema. The description does not explicitly explain that job_id identifies the transcription to stop, so it fails to compensate for the missing parameter documentation.

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 and resource: stop a transcription when the user cancels or corrects it. It also scopes the operation to include jobs awaiting instruments or price, which distinguishes it from a generic cancellation tool.

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?

It explicitly says when to stop a transcription, including cancellations and corrections, and when not to stop it for slowness. It also routes the agent to the follow-up workflow: correct the instruments and transcribe again from that task with the full list and a new price.

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