transcription_api_v1_audio_transcriptions_post

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

No annotations are provided, and the description gives no behavioral information. It does not disclose that the tool accepts audio files, outputs text, or any side effects, rate limits, or required permissions.

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?

While extremely short (one word), it is not concise but rather under-specified. It lacks essential information and does not earn its place by providing any useful content.

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 the two parameters (one required) and the lack of output schema and annotations, the description is completely inadequate. It fails to describe what the tool does, what input is expected, or what the output is.

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?

With 0% schema description coverage, the description adds no meaning to the parameters. It does not explain that 'file' is an audio file for transcription or that 'language' is optional for specifying the source language.

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 is the single word 'Transcription', which merely restates the tool name without specifying the action (e.g., transcribe audio to text) or distinguishing it from siblings like speech_api_v1_audio_speech_post. It fails to clarify that this tool converts audio files into text.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it is for transcribing audio files, nor does it differentiate from other audio or processing tools in the sibling list.

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