Transcribe

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it doesn't say what the backend must be initialized with, whether transcription is synchronous or long-running, what the output looks like, or what happens on failure.

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?

It is a short, front-loaded sentence with no filler, so it isn't bloated. But brevity here reflects under-specification rather than economy, given the tool's complexity.

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?

A 7-parameter transcription tool with no output schema, no annotated output description, and no parameter documentation in either schema or description. The description does not give the agent enough to call this correctly.

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?

There are 7 parameters with 0% schema description coverage, and the description mentions none of them. Key options like task ('transcribe' vs presumably 'translate'), language, word_timestamps, initial_prompt, and temperature are left entirely opaque.

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 names a specific verb and resource ('Transcribe the audio file'), but says nothing that distinguishes it from the many sibling transcription tools (transcribe_audio, transcribe_media_transcribe_segments). 'The initialized backend' hints at server state but doesn't clarify scope or output.

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?

No guidance on when to pick this tool over transcribe_audio or transcribe_media_transcribe_segments, and no explicit statement that initialization must happen first (only implied by 'initialized backend'). The agent must guess the ordering and the alternative.

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