get_voice

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It does not mention that the tool is read-only, safe, or any potential side effects, rate limits, or auth requirements. While the description correctly describes the output, it lacks explicit behavioral transparency beyond that.

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 concise (two sentences), with the first sentence clearly stating the purpose and listing return fields, and the second providing a relevant sibling tool reference. No unnecessary words or repetition.

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?

An output schema exists, so the description does not need to detail return format, but it still lists key fields. It guides users to preview_voice for audio URLs. Given the simplicity of the tool (one required parameter, read operation), the description is largely complete, though it omits error handling or source of voice_id.

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 only parameter is voice_id, and the schema has no description (0% coverage). The description mentions 'by voice_id' but does not explain what a voice_id is, how to obtain it, or any constraints. It adds minimal value beyond the schema itself.

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 the tool fetches full detail for a single voice by voice_id, listing the returned fields. It distinguishes from sibling tool preview_voice, which provides actual audio URLs.

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 explicitly directs users to preview_voice for sample audio URLs, providing clear guidance on when to use this tool vs an alternative. However, it does not explicitly state when not to use this tool (e.g., for searching or listing voices), but the context implies it.

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