create_voice_from_preview

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

The description discloses that the tool makes an API call to ElevenLabs and may incur costs, which is behavioral information beyond the annotations. It also mentions the dependency on `text_to_voice`, adding 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 concise: two brief sentences plus a warning. It is front-loaded with the purpose and has no unnecessary words.

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 adds a voice to a library, the description lacks details about the scope (e.g., user's library), side effects (e.g., overwriting), or confirmation of success. The output schema exists but the description could offer more context.

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 description explains that `generated_voice_id` comes from `text_to_voice`, adding context beyond the schema. However, it does not explain `voice_name` or `voice_description`, and the schema provides no descriptions, so only partial parameter semantics are covered.

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 tool's purpose: 'Add a generated voice to the voice library.' It also specifies the dependency on the `text_to_voice` tool, which distinguishes it from other voice management tools.

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 includes a cost warning that advises using the tool only when explicitly requested by the user, providing a clear usage guideline. However, it does not compare with other tools like voice_clone or specify when not to use it.

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