openai_create_transcription

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only notes 'using OpenAI Whisper', but fails to mention key behaviors like mutation (transcription is read-only), authentication needs beyond the api_key parameter, or potential rate limits or file size restrictions.

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 a single sentence, which is concise but overly minimal. It could include additional context without becoming verbose, such as mentioning supported audio formats or return types.

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 tool has 8 parameters, no output schema, and no annotations, the description is too brief. It does not explain the return format, error handling, or operational constraints like file size or duration limits, leaving significant gaps for the agent.

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 description coverage is 50% (4 of 8 parameters documented). The description does not add any parameter-level details beyond what the schema already provides. For an 8-parameter tool, the description should compensate for the undocumented parameters, but it does not.

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's purpose: 'Transcribe audio to text using OpenAI Whisper.' It specifies the verb (transcribe), resource (audio), and model (Whisper), making it distinct from sibling tools like openai_chat_completion or assemblyai_transcribe.

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 provides no guidance on when to use this tool versus alternatives, such as other transcription tools like assemblyai_transcribe. It lacks context on prerequisites, limitations, or use cases.

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