transcribe_urls_batch

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

Discloses concurrency and failure behavior beyond annotations (readOnlyHint=false, destructiveHint=false). Adds value explaining parallel execution and partial failures.

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, no filler, front-loaded with purpose, then details. Every word adds value.

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?

Covers key behavioral aspects for a batch tool. Missing output schema description, but the tool likely returns results immediately; context is adequate for invocation decisions.

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?

All parameters have schema descriptions (100% coverage). The description adds the batch context but does not elaborate on diarize, language, or word_timestamps beyond the schema.

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?

Description clearly states the verb 'transcribe' and the resource 'a list of URLs', distinguishing it from sibling tools like transcribe_url (single URL) and transcribe_file (file).

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?

Explicitly mentions concurrency, batch size limit, and per-URL failure handling, providing good usage context. Could be improved by explicitly stating when not to use (e.g., single URLs).

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