List voices

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

No annotations are provided, so the description must disclose behavioral traits. It only states the functional purpose and does not mention that the operation is read-only, requires no authentication, has no side effects, or any potential rate limits. For a listing tool, the absence of such context is a notable gap.

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 a single, tightly worded sentence with no extraneous content. It is front-loaded with the core function, achieving maximum brevity without sacrificing clarity.

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 parameterless tool with an output schema, the description is largely complete for invocation purposes. The output schema presumably details the return format, and the description covers the what and scope. However, it lacks usage routing context, which is more appropriately addressed under usage guidelines, so this dimension is adequately covered.

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, and the input schema is empty. With no parameters to document, the description cannot add meaning beyond the schema, warranting the baseline score of 4. There is nothing to compensate for because there are no parameters.

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 'Names of every voice profile the server can speak in' clearly identifies the tool as a listing operation for voice profiles. The resource and scope are explicit, and it distinguishes itself from siblings 'synthesize' and 'describe' by its focus on enumeration rather than generation or analysis.

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 provides no guidance on when to use this tool versus its siblings. It does not mention that it should be called before 'synthesize' to select a voice, nor does it state any exclusions or conditions. An agent receives no strategic context for choosing this tool.

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