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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds useful behavioral context by listing the specific outputs (payable amount, balance, welcome-credit effect, shortfall, feasibility, private link) and the condition for the link (when more balance is needed). This goes beyond the annotation basics.

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 a single, efficient sentence that front-loads the critical usage timing ('Call after inspecting the audio and before creating a job') and then lists the returned items. There is zero fluff; every word adds value.

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 that an output schema exists (as indicated in context signals), the description does not need to detail the return format. It covers the key usage context, the timing, the outputs, and the conditional private link. It feels complete for the tool's simple purpose, though it could benefit from a note on parameter relevance.

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?

With schema description coverage at 0%, the description must compensate, but it does not explain what 'epochs' and 'durationSeconds' mean or how they influence the quote. The tool name and context imply they are training parameters, but no explicit semantics are given. This is a significant gap for an agent to correctly construct the inputs.

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 clear specific action: quote an RVC training job. It explicitly names the verb 'Quote' and the resource 'RVC training job', and distinguishes it from siblings like create_training_job by saying it returns the payable amount and feasibility before creation. The mention of 'exact payable amount' and 'feasibility' makes the purpose unambiguous.

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 provides a clear usage context: 'Call after inspecting the audio and before creating a job.' This tells the agent when in the workflow to invoke it, but does not explicitly name alternatives or conditions when not to use it. Sibling tools like get_training_requirements exist, but no exclusion is given.

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