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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior — results widen to all account keys when the key is claimed, and the download URL is ephemeral ('while the result is still available'). It says nothing about ordering beyond 'recent' or the pagination model the cursor implies.

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?

Two sentences, zero waste, with the scope rule front-loaded and the ephemeral-URL caveat second. Nothing is repeated from the title or annotations.

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 read-only list tool with annotations covering safety and no output schema, the description covers scope and the notable download-URL caveat, but leaves the response shape (job fields, ordering) and all pagination behavior unexplained. Adequate to call, thin on how to page through or interpret results.

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?

Both parameters (limit, cursor) have zero schema description coverage and are never mentioned in the description. An agent gets no default page size, no maximum (100 is only in the schema), and no explanation of cursor semantics or whether 'recent' means a bounded time window — a real gap at 0% coverage.

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 clear verb ('list') plus the resource ('transcription and burn jobs') and even scopes the result set by key ownership. It never names the closest sibling, get_job, so an agent must infer on its own that get_job returns a single job rather than a collection.

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 context ('recent jobs') implies when to call it and the paid-key scope note hints at account-level behavior, but there is no explicit 'use X instead when Y'. In particular, nothing routes the agent to get_job for a specific job's details or status.

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