tool_list_voices

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

No annotations are provided, so the description carries the behavioral transparency burden. It clearly presents this as a read-only listing operation and discloses the return shape: 'list of dicts, each with name, description, language, source, created_at.' It does not discuss auth or rate limits, but those are not pressing for a no-parameter list tool.

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 compact and front-loaded: the core action appears in the first sentence, the return format is summarized in one line, and the usage guidance is a single actionable sentence. No words are wasted.

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 no-parameter listing tool, the description is complete. It states what the tool lists, what it returns, and provides a concrete workflow context with synthesize_speech. There are no gaps that would prevent an agent from calling it correctly.

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 tool has zero parameters, so the baseline is 4. The description adds useful context by explaining that the returned voice_name values are what should be passed to synthesize_speech, which is more helpful than the empty input schema alone.

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 opens with a specific verb and resource: 'List all saved voice profiles.' It also specifies the return fields and states the tool's role in discovering available voice_name values, making it clearly distinct from sibling tools like tool_get_voice_info or tool_synthesize_speech.

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?

It gives explicit usage context: 'Use this to discover available voice_name values before calling synthesize_speech.' This clearly tells the agent when to use this tool relative to synthesis, though it does not explicitly state when not to use it or mention alternatives like tool_get_voice_info.

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