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

The annotations already establish that this is a safe read-only operation, and the description adds useful context: the voices are consent-based, the lookup is free, and an empty result means the user has no recorded voice yet. It does not discuss pagination or response shape, but the output schema covers 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 purpose is front-loaded and the empty-state guidance is useful. There is minor parenthetical detail and the sentences split across purpose, cost, and next-step usage, but no significant wasted text.

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 one-parameter list tool with a full output schema and read-only annotations, the description covers purpose, usage, cost, and the important empty-state next action. Nothing material is missing for correct invocation.

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, `workspaceId`, is fully documented in the schema, including when it can be omitted. The description does not add further workspace-scoping semantics, so the schema is doing the substantive parameter work.

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 identifies the exact resource: the user's own cloned voices in the current workspace, and explicitly distinguishes them from Ignix voices. It also connects the result to the `generate_voiceover` workflow, so an agent can tell what this tool returns and why it matters.

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?

It gives a clear usage path: call this to get a voice id, then pass it as `myVoiceId` to `generate_voiceover` when the user wants their real voice instead of an Ignix voice. It also explains the empty-state path, though it does not explicitly state when not to use the tool or name every relevant alternative.

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