search_voices

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

No annotations provided, so description carries full burden. It discloses read-only behavior, case-insensitive partial matching for query, and country code examples. However, it lacks details on pagination or result limits, which could affect agent decisions.

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 short introductory sentences followed by a concise args list. No redundant or vague wording. Every sentence provides value. Front-loaded with purpose, then details.

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 3 optional parameters, an output schema for return type, and no required parameters, the description covers all essential aspects: what the tool does, how to filter, and expected behavior. No critical gaps.

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?

Input schema has 0% description coverage, making description essential. It adds specifics: query is case-insensitive partial match, country includes examples (US, GB, FR, DE, PT), gender is MALE or FEMALE. This is significantly more informative than the 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 clearly states 'Search voices by name, country, or gender' and explains it fetches all voices and filters. This distinguishes it from siblings like list_voices (which likely returns all without filtering).

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 implies use when filtering voices by query, country, or gender but does not explicitly state when not to use it or mention alternatives. No exclusions or when-to-use guidance beyond the implicit purpose.

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