Tts Create

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds context that it produces standalone speech audio, but does not disclose side effects, output format, or any required permissions beyond what annotations provide. It does not contradict the annotations.

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?

Two sentences, front-loaded with the primary action, and immediately followed by clear exclusion/alternative guidance. No wasted 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?

While purpose and usage are well covered, the description omits essential invocation details: no explanation of the five parameters, no return value description (no output schema), and no mention of optional parameters or performance/cost implications. The agent lacks enough information to confidently call the tool without further inquiry.

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?

With 0% schema description coverage and zero parameter descriptions in the tool description, the agent has no guidance on the meaning of stability or similarityBoost, and only implicit hints about script (text) and voiceId from the example mention of create-lipsync. The description fails to compensate for the schema's lack of parameter documentation.

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 synthesizes standalone speech audio from text, using a specific verb and resource. It directly distinguishes itself from the sibling create-lipsync tool, so the agent knows exactly when to choose this tool.

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 states when to use ('only when the user specifically asks for an audio file or voice preview') and when not to use ('Do not use for lipsync requests'), naming the alternative tool (create-lipsync) and its relevant parameters. This is exemplary guidance.

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