Batch-transcribe a podcast feed

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

Annotations already indicate idempotent and non-destructive behavior. The description adds 'Paid capability (throughput/abuse gate)' hinting at billing/rate limits, but does not elaborate on job creation or credit consumption. With annotations covering safety, this adds some value.

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 concise sentences with no wasted words. Key information is front-loaded: batch-transcribe a whole podcast feed. Efficient and well-structured.

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 no output schema, the description mentions return of job IDs. It covers the main purpose and parameter usage adequately for a batch tool of this complexity, though could add note on error handling.

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 coverage is 50%; description clarifies that 'latest' limits episodes, but does not explain 'diarize' or provide further semantics for 'idempotency_key' beyond schema. It partially compensates for the gap but not fully.

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 it batch-transcribes a podcast feed by fanning out episodes to individual jobs, with the option to limit to latest N episodes, and returns job IDs. This distinguishes it from sibling tools like 'transcribe' which likely handles single files.

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 implies use for whole feed batch processing, and mentions it as a paid capability. However, it does not explicitly contrast with alternatives like 'transcribe' or list tools, missing a clear 'when to use' statement.

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