text_to_speech

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description is not required to reiterate those. It adds value by disclosing that no API key is needed and that the output is base64-encoded MP3, which is not evident from annotations alone.

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 extremely concise, using just two sentences to convey the core function and a key requirement. Every sentence serves a purpose, and the most critical information is front-loaded.

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 that an output schema exists, the description does not need to elaborate on return values. It covers the essential purpose and the 'no API key' fact, but lacks any guidance on parameter usage, potential limitations (e.g., text length), or how to choose voices, which would enhance completeness for an 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?

With 0% schema description coverage, the description should compensate by explaining parameters, but it does not mention text, speed, or voice at all. The agent receives no information about default values, valid ranges, or how parameters affect the output, leaving a significant gap.

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 converts text to speech and returns base64 encoded MP3 audio, which identifies the main action and output. However, it does not differentiate this tool from its sibling 'text_to_speech_file' nor specify the scenario for using one over the other.

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 implies usage by stating the core function and adding 'No API Key required' as a convenience hint. Yet it offers no explicit guidance on when to choose this tool over 'text_to_speech_file' or 'list_voices', and lacks any exclusions or prerequisites.

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