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

Annotations only declare it is a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false); the description adds substantive context beyond that — enrollment requires a voice recording and consent and happens on the web, clones require an active plan, and outputs carry an AI-voice disclosure.

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?

Four sentences, no filler, and front-loaded: what it lists, what to do with the result, then the constraints (read-only enrollment, plan requirement, disclosure). Each sentence carries distinct operational 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?

An output schema exists, so return-value documentation is not needed. What an agent needs beyond that — eligibility gating, the enrollment path, and where the returned ids go next — is all present.

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?

Zero input parameters, so the baseline is 4. The description does add meaning by naming 'voiceCloneId' as the identifier these voices produce and consume elsewhere, which is not visible in the empty input schema.

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+resource ('List your cloned narration voices') plus the qualifying dimension it returns ('whether this account can use them'). That distinguishes it from the adjacent listing tools in the same family (list_topic_short_styles, list_storyboard_voices, list_audio_lab_voices), which cover different resource types.

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?

Explicitly prescribes the downstream action: 'Pass a ready clone id as voiceCloneId to quote_topic_short and generate_topic_short.' It also states the condition under which this tool yields nothing actionable (no active plan) and redirects enrollment to the web workspace, so the agent knows what this tool cannot do.

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