tts_save_audio

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

With no annotations provided, the description carries the full behavioral burden, but it only states the basic action. It fails to disclose that this writes a file to disk, any permissions or limitations, or whether it overwrites existing files—important for an AI agent to know.

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 concise sentence with no redundant words. It front-loads the primary action and is appropriately sized for a simple tool, though it could include more detail without losing conciseness.

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?

Despite the schema covering parameters, the description lacks essential context for an agent deciding to invoke this tool. It doesn't explain the output (e.g., confirmed file path), usage scenarios, or caveats like file overwriting. The tool is relatively complex (5 params, no output schema), and the description under-delivers.

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?

The input schema already provides descriptive text for all five parameters (e.g., 'Speaking rate in words per minute', 'Audio format: aiff, wav, mp4'), so the description adds no additional semantic value beyond what's in the 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?

The description clearly states the tool's function—converting text to speech and saving to a file—which distinguishes it from sibling tools like tts_speak (likely playback) and tts_list_voices. However, it doesn't mention the selectable formats or voice options, which are present in the schema.

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 its siblings (tts_speak, tts_list_voices, etc.). It doesn't specify use cases such as 'when you need a playable file' or 'for audio file archives.'

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