list_voices

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

With no annotations, the description still carries useful behavioral signal: the GET verb implies a non-destructive read, and 'authenticated' flags an auth requirement. It says nothing about pagination behavior, default page size, ordering of results, or what the catalog entries contain, which is a notable gap for a paginated 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?

A single sentence with no padding and the resource immediately front-loaded, so nothing is wasted. However, the brevity comes at the cost of substance rather than through efficient packing, so it reads as under-specified rather than tight.

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?

A paginated catalog-list tool with three undocumented parameters, no annotations, and no output schema needs at least an explanation of paging and what is returned. The definition supplies only the endpoint name, which is not enough to call it confidently or correctly on the first attempt.

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 0%, so the description must compensate and does not. The word 'Search' faintly gestures at the 'search' parameter but gives no guidance on matching semantics, and neither 'page_size' nor 'next_page_token' is mentioned, leaving all three parameters' purpose to be guessed from their names.

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?

States a specific verb ('Search') and a specific resource ('the authenticated voice catalog'), and names the underlying endpoint GET /v2/voices, so an agent knows this browses voices rather than creating, cloning, or fetching a single one (get_voice, clone_voice, design_voice). It stops short of explicitly naming those siblings, which keeps it at 4.

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?

There is no when-to-use guidance, no statement of when to prefer this over get_voice or the voice-creation tools, and no prerequisites beyond the word 'authenticated'. Usage must be inferred entirely from the tool name and the resource noun.

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