listClonedVoices

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

Annotations cover the safety profile (readOnlyHint, openWorldHint=false), so the bar is lower. The description still adds real context: deterministic oldest-first ordering, cursor-loop pagination semantics, and a state gate (only ready voices have a usable voice_id).

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 ordering and pagination rule come first, which is the right priority, and the whole thing is three short sentences. The trailing '(Tags: Voice cloning)' is filler that earns nothing.

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?

With no output schema, the description carries the return-value burden and does so adequately by naming next_cursor and the ready/voice_id fields. An agent has enough to page correctly and to consume results, though the full voice object shape is never sketched.

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%, so both parameters are already documented with defaults, max, and opaque-cursor notes. The description restates the cursor contract but adds no new syntax or constraints beyond the schema, making the baseline 3 correct.

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 states a specific resource (cloned voices) and result ordering (oldest first), which cleanly separates it from listVoices and getClonedVoice. It never uses an explicit verb like "list," but the phrasing leaves no ambiguity about what is returned.

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 concrete call procedure (call with no cursor, then loop on next_cursor until null) and explains the downstream action once a voice is ready (use voice_id with provider cartesia). It does not, however, say when to prefer this over listVoices or getClonedVoice.

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