design_voice

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

Discloses that previews are generated and saved to files, and that they are not permanent unless explicitly saved via sibling. No annotations exist, so description covers key behaviors. Could be more explicit about the temporary nature of previews.

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?

Structured into title, paragraph, Args list, and Returns line. No redundant information. Every sentence adds value.

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 an output schema present, the description offers adequate return information (IDs and paths). Covers main purpose, parameters, and follow-up action. Lacks error handling or edge cases, but acceptable for a design tool.

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?

Adds meaning to all four parameters beyond the schema: provides example for voice_description, recommendation for text, default behavior for model_id, and explanation for auto_generate_text. Fully compensates for 0% schema description 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?

Clearly states the tool designs candidate voices from a text description, generates previews, and saves audio. Distinguishes from sibling tool create_voice_from_preview which is used for permanent retention.

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?

Explicitly describes when to use (designing voices from description) and provides an alternative (use create_voice_from_preview to keep permanently). Also recommends minimum text length.

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