get_voices

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

No annotations are provided, so the description must cover behavioral traits. It states it lists voices with optional cloned voices requiring auth, but does not specify pagination, rate limits, or whether the base list requires authentication. A 3 is adequate given the simple read-only nature.

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 two sentences with a brief note about Lightning V3.1, efficiently conveying purpose and usage. It is front-loaded and compact, though the note could be integrated more smoothly.

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 low complexity (list with three optional filter parameters) and no output schema, the description sufficiently explains both inputs and the structure of the return value (IDs, names, gender, language, supported models). No gaps are present.

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%. The description repeats the schema's parameter descriptions without adding new semantics, so it meets the baseline but adds no extra value for parameter understanding.

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 'List available voices for agents' with specific return fields (IDs, names, gender, language, supported models). It also distinguishes from siblings by noting how the voiceId connects to update_agent_config.

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 explains how to use the returned voiceId with another tool (update_agent_config) and mentions the special case for Lightning V3.1 Pro voices. It lacks explicit when-not-to-use guidance, but no sibling tool duplicates this functionality.

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