Generate speech

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

With no annotations at all, the description carries the full burden. It does disclose the key side effect ('Saves an audio file locally'), which is real behavioral value for a write-to-disk tool, but it says nothing about auth (Poe API key), network/rate-limit behavior, cost, or text-length limits.

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?

Two tightly packed sentences with zero filler; the core action and its output location lead, and the model options follow as supporting detail.

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 6-parameter tool with a nested `parameters` object, no output schema, and no annotations, the description covers the primary output (a locally saved audio file) but leaves the caller without auth prerequisites, failure modes (unsupported bot/voice), or any indication of what is returned on success.

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%, so the baseline is 3, but the description genuinely adds meaning the schema lacks: the default model ('default: ElevenLabs') and additional valid bot names (Hailuo-Speech-02, OpenAI TTS) beyond the schema's two examples. It does not clarify `voice` behavior when a bot lacks voice selection.

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 gives a specific verb+resource pair ('Turn text into spoken audio') and names the concrete backend family (Poe TTS bots, default ElevenLabs). The output modality implicitly separates it from generate_image/generate_video/generate_music, but it never explicitly differentiates itself from the general-purpose sibling generate_with_poe_bot.

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?

Usage is only implied: use this when you want speech from text. There is no when-not guidance and no statement about when to prefer this over generate_with_poe_bot, even though both talk to Poe bots. The bot-name list gives model-selection guidance but not tool-selection guidance.

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