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

The description adds the return format ('mp3 in base64'), which is useful. However, despite annotations showing readOnlyHint=false and idempotentHint=false, it does not disclose side effects, caching, permissions, or what happens on repeated calls.

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 single sentence is front-loaded but under-specifies rather than concisely covering the necessary ground. It omits essential usage and parameter details, so brevity here is a liability.

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?

With no output schema, one undocumented parameter, and sparse annotations, the description should carry more burden. It mentions the mp3/base64 return format but leaves out what the tool actually does, when to use it, and how to supply the text parameter.

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 0%, and the only parameter ('text') is undocumented in the schema. The description implies 'text' is a phrase, but does not explain constraints such as language, length, or expected input format.

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 restates the tool name and title ('Reference audio') and adds only 'of a phrase (mp3 in base64)'. It does not state a verb or explain whether the tool generates, retrieves, or converts audio, so the purpose remains largely tautological.

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 the many sibling audio tools such as dialogue_audio, lesson_audio, quiz_audio, or practice_phrase. The description provides no context, prerequisites, or exclusions.

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