elevenlabs_get_voice_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'get detailed information,' which implies a read operation, but it does not explicitly state non-destructiveness, return format, or any error behavior. The lack of annotation and minimal description leaves the agent guessing about what 'detailed' includes.

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 concise sentence with no wasted words, and it front-loads the core action. However, it is so terse that it misses an opportunity to enrich the context within the same length.

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 simple read tool with one fully documented parameter, the description is minimally sufficient. However, it lacks clarity on what 'detailed information' entails (e.g., which fields are returned) and omits any note on auth or error conditions, leaving gaps for an agent deciding between this and list_voices.

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 schema fully describes voice_id as 'ID of the voice to get information about' (100% coverage), so the baseline is 3. The description adds no extra semantic value beyond the schema's own description.

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 'Get detailed information about a specific voice' uses a specific verb (get) and resource (specific voice), making it clear this retrieves one voice's details. The contrast with the sibling 'elevenlabs_list_voices' is implicit via 'specific', but it does not explicitly differentiate alternatives.

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 gives no explicit guidance about when to use this tool versus siblings like list_voices or text_to_speech. The word 'specific' implies a single-voice lookup, but there is no stated condition or alternative recommendation.

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