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

The description reveals a non-obvious side effect: each download consumes source-audio duration from the account's conversion-download minutes. It also discloses the duplicate-file behavior and the need to set confirmRepeat true, which is meaningful behavioral context beyond the annotations.

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?

Three concise sentences, each carrying necessary information: usage precondition, billing side effect, and duplicate retry rule. No redundant or filler content.

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 download operation with an output schema and annotations already present, the description covers the key context: when to call, what cost is incurred, and how to handle duplicate downloads. It provides enough behavioral and procedural context for an agent to invoke the tool correctly.

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 already describes kind and confirmRepeat, and the description reinforces confirmRepeat's purpose. However, with only 50% schema description coverage, conversionId and eventId remain largely undocumented by both the schema and the description. The description adds some value but does not fully compensate for those gaps.

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 verb ('Download'), a specific resource ('completed voice conversion output'), and the exact trigger condition ('Use after get_voice_conversion says the job is complete'). This makes the tool's purpose distinct from the sibling creation and status-checking tools.

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 clear when-to-use guidance: only after the job is complete and the user wants cleaned or standard output. It also specifies the duplicate-download protocol. It does not explicitly name an alternative to use when the job is still running, but that is strongly implied by the precondition.

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