elevenlabs_generate_speech

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

With no annotations, the description carries the burden and does disclose key traits: it writes a file to disk, may mutate the Premiere project, and requires an ELEVENLABS_API_KEY. It is slightly imprecise about defaults, describing import and timeline placement as one optional step even though they are two independent flags (import_to_premiere defaults true, add_to_timeline defaults false).

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?

Three short sentences with the core action front-loaded and the environment prerequisite trailing. No filler, though the middle sentence slightly muddles two separate behaviors (import vs. timeline placement).

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 12-parameter tool with no annotations and no output schema, the description omits useful context: where the audio file is saved, whether the call is billed/network-bound, and what the tool returns (path or project item). The schema covers parameter details, but the result contract is left to inference.

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 every parameter including ranges and defaults is already documented in structured data. The description adds only the general notion of optional Premiere import and timeline placement, no new meaning per parameter — baseline 3 applies.

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?

States a specific verb and resource ('Generate speech audio from text using ElevenLabs AI') plus the downstream side effect of saving/importing into Premiere. It is clearly distinguishable from elevenlabs_list_voices, but it never names or contrasts with the closest sibling, elevenlabs_generate_captions_voice.

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 implied by 'from text' and the timeline-import option, but there is no explicit when-to-use or when-not guidance, and nothing tells the agent when to pick this over elevenlabs_generate_captions_voice or how to chain it after elevenlabs_list_voices.

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