elevenlabs_text_to_speech

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'convert text to speech' without disclosing whether it writes to a file, returns audio data, handles output_file, sync/async, format details, or other side effects. This is minimal behavioral transparency.

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 unnecessary words, making it front-loaded and easy to parse. However, given the tool's parameter complexity, this brevity borders on under-specification, but conciseness itself is good.

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?

The tool has 6 parameters, no output schema, and no annotations. The description only states the core capability without explaining output behavior, file handling, or the distinction from streaming. This leaves important gaps for an agent selecting and invoking the tool correctly.

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 has 100% description coverage for all 6 parameters, so the schema already explains parameters like text, model_id, voice_id, etc. The description adds no additional meaning beyond the schema, which meets the baseline of 3 for high schema coverage.

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 states the primary action clearly ('Convert text to speech'), but it does not differentiate from the sibling tool elevenlabs_stream_text_to_speech, which performs a similar streaming variant. Therefore it is clear but lacks sibling differentiation.

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 information about when to use this tool versus alternatives. No mention of streaming vs file output, use cases, or prerequisites. The description provides only the basic function, leaving the agent to infer usage.

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