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

Beyond the annotations, the description discloses that there is no charge, that the call creates nothing, and that the output quote_id and credits must be handed to create_voiceover. That is the key behavioral context for a pricing call. There is a mild tension with readOnlyHint=false, since a quote that charges nothing reads as read-only, but the hint is plausibly conservative because the call is non-idempotent; this is a gap in coherence, not a flat contradiction.

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 front-loads the usage trigger and then chains the pricing step to create_voiceover. It is dense but nearly every clause earns its place; the parenthetical about a quote creating nothing is slightly redundant with the earlier 'Nothing is charged', so it is not perfectly tight.

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 the description need not explain the return values, and it names quote_id and credits only where the chaining logic requires it. With 6 parameters fully described by the schema, a complete usage trigger, a no-charge disclosure, and an explicit next step, nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100%, so all six parameters are already documented, including defaults, ranges, and the voice_id format. The description adds only a plain-language restatement of text and voice, with no extra format or constraint detail. The baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource: it prices a voice-over in Deepnia credits, before anything is created, and it ties that price to the exact text and chosen voice. That scope clearly separates it from create_voiceover, which actually produces the audio, and from the quote_image and quote_video siblings, which cover other media.

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 says exactly when to use this tool (the user wants a voice-over and needs the price first), what it does not do (nothing is charged, and a quote alone creates nothing), and what to do next (show the price, get acceptance, then call create_voiceover with the returned quote_id and credits). The alternative sibling and the condition that selects it are named explicitly.

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