transcribe_audio_file

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

Discloses engine (Whisper), routing (WebSocket), return fields (transcript, timing diagnostics), and file/processing caps. No annotations exist, but description adequately covers behavioral traits without contradictions.

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 concise at about 4 sentences, front-loaded with the main verb and object. Every sentence adds value, though the last sentence could be integrated.

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?

No output schema exists, but the description fully specifies return fields and diagnostic details. It covers format support, engine, limits, and usage pattern, making it complete for an agent's decision-making.

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 100% with descriptions for both parameters. The description adds context about ffmpeg format support and language auto-detection, but these are incremental to the schema. Baseline 3 is appropriate.

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 tool transcribes an audio file at a given path, explicitly distinguishes from bulk processing needs by directing agents to iterate per file, and no sibling tool offers transcription.

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?

Provides clear context for when to use the tool (individual files, not bulk), and lists technical limits (500MB, 60s ffmpeg, 120s WS). However, it does not explicitly exclude alternative tools since none exist.

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