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

The description adds valuable behavioral context beyond the annotations: it states that the tool returns a one-time PUT upload instruction, implying a temporary upload URL and requiring an external upload step. It also hints at the tool being non-mutating (it only prepares) and non-destructive, aligning with the annotations (readOnlyHint=false, destructiveHint=false). However, it does not detail authentication requirements or what happens if the upload is not completed, which would be extra context.

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 description is two sentences, front-loaded with the primary purpose and usage trigger, and clearly explains the return and next step. It contains zero filler and every sentence adds value, making it an excellent example of conciseness and structure.

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?

Given the presence of an output schema (which likely describes the PUT upload instruction) and the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description is fairly complete. It explains the purpose, the trigger, and the follow-up action. However, it could briefly mention that the upload URL is temporary or that the tool does not actually upload the file, which would improve completeness, but the current description covers the essential workflow.

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 provides clear descriptions for both parameters: fileName as the original .pth or .zip filename, and sizeBytes with a max limit. The description adds no additional parameter-specific meaning beyond what the schema states, and with schema coverage at 50% (the schema describes both parameters but may not cover all aspects like encoding or extensions), the baseline 3 is appropriate.

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 states the tool's purpose: to prepare a private RVC model upload, specifying what the user wants (convert with an existing private RVC .pth file or ZIP) and that it returns a one-time PUT upload instruction. This distinguishes it from siblings like creating a training job or converting with a library voice, and it is consistent with the name.

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 explicitly states when to use this tool ('when the user wants to convert with an existing private RVC .pth file or complete model ZIP instead of a voice trained in their NiceVois library') and provides a clear next step ('After uploading, call list_voice_models to select the imported voice'). This provides strong usage guidance and names an alternative action (using a library voice) and a follow-up action.

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