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

Discloses model, accepted URL formats, output (transcript, language, duration), and summarize parameter behavior. No annotations provided, so description carries full burden; covers key aspects but omits rate limits or auth requirements.

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?

Short, front-loaded sentences. Every sentence adds value: function, model, accepted formats, output, usage examples. No redundancy.

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?

For a simple tool with fully described parameters and clear usage guidance, the description is complete. Covers inputs, outputs, and typical use cases. No output schema needed.

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 100%, baseline 3. Description repeats schema details for each parameter (language hint, summarize default) and adds context about output. Does not provide additional parameter meaning beyond 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 starts with 'Transcribe any audio file or voice recording to text' – a specific verb+resource. Specifies model (Groq Whisper) and formats. No sibling transcription tool, so it is clearly distinguished.

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 states when to use: 'when user shares an audio link, voice memo URL, podcast clip, meeting recording, or says transcribe this'. Does not mention when not to use (e.g., for translation), but given unique functionality, it is clear.

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