get_voice

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds context the annotations do not: that the call does NOT consume credits (a billing concern) and that the payload includes a preview MP3 URL. It stops short of describing error behavior for unknown voice IDs or whether metadata is cached/live.

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 sentences, zero filler, with the core purpose front-loaded before the usage routing. Both sentences earn their place by carrying distinct information.

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 2-required-param read with no output schema, the description covers what it returns (metadata + preview MP3 URL), when to call it, and the cost profile. Missing only edge-case guidance such as behavior on an invalid voiceId or cross-provider ID mismatch.

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 coverage is 100%, and the schema already documents both provider and voiceId with a concrete example. The description adds no parameter-level meaning (e.g. that provider and voiceId must be a mutually consistent pair), so baseline 3 applies.

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 and resource ('Fetch full metadata + a preview MP3 URL for a single voice'), and explicitly scopes it to one voice as opposed to the list/search siblings. An agent can distinguish it from search_voices and list_provider_voices without opening a schema.

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?

Gives two concrete trigger conditions: after the user picks from search_voices / list_provider_voices, or when they paste a voice ID. It names the upstream alternatives and the condition that selects this tool, leaving nothing to inference.

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