text_to_speech

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

No annotations provided. Description mentions async task creation and return values, but omits default wait behavior, polling, or permission requirements. Should disclose more behavioral traits.

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?

Single sentence, but lacks structure. Could include bullet points or separate return info. Acceptable for a simple tool but could be better organized.

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 5 parameters, no output schema, and no annotations, the description is incomplete. Lacks details on async workflow, polling, and return format. Users may need to guess behavior.

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 coverage is 40% (only wait and model have descriptions). Description adds no extra meaning beyond 'text to speech'. Relies too heavily on minimal 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 clearly states it creates a ElevenLabs text-to-speech task and returns a task id, status, and output URLs. It differentiates from sibling tools like speech_to_text and text_to_dialogue, but could be more explicit about the async nature.

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?

No guidance on when to use this tool vs siblings. Implicitly it's for text-to-speech, but no exclusions or alternatives mentioned.

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