elevenlabs_stream_text_to_speech

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that the tool performs streaming, which implies incremental generation and suitability for long texts. However, it does not elaborate on output behavior (e.g., whether it waits for full audio or writes progressively), potential errors, or resource implications, leaving some behavioral gaps.

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, front-loaded sentence with no wasted words. It immediately states the action and the key differentiator ('streaming'), followed by practical use cases. Highly concise and well-structured.

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 the tool's moderate complexity (4 parameters, no output schema) and full schema coverage, the description covers the essential purpose and usage context. It could mention more about stream behavior or error handling, but for a straightforward text-to-speech tool, it is sufficiently complete.

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% parameter description coverage, so the schema already documents each parameter's meaning. The description does not add specific parameter semantics beyond the schema, though the streaming context indirectly explains why an output file path is needed. Baseline 3 is appropriate.

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 verb 'Convert' and resource 'text to speech', and distinguishes itself from the non-streaming sibling 'elevenlabs_text_to_speech' by emphasizing 'streaming' and specifying 'for longer texts or real-time generation'. This makes the tool's unique purpose immediately clear.

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 clear usage context by stating 'for longer texts or real-time generation', which indicates when streaming is appropriate. It does not explicitly name alternative tools or state when not to use it, but the context is enough to guide the agent.

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