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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description reinforces this with 'sans rien enregistrer' and adds value by disclosing what is bundled into the price (quantity discount included, shipping fees, delivery estimate), which annotations cannot convey.

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?

Two short sentences, no filler, with the output content front-loaded and the single actionable hint (postal_code) placed last. Every clause earns its place.

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 an 11-parameter nested tool with no output schema, the description does state the shape of the result (price, shipping, estimated date), which is the main missing piece. It does not address the texts/pieces interaction or defaults, but the schema documents those thoroughly at 91% coverage.

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 91%, so the schema already documents category, postal_code, sizes, pieces, texts and the rest. The description only adds the conditional link 'postal_code → delivery date', which the schema property description also states, so it adds little beyond the structured fields.

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?

States precisely what is computed and returned: exact TTC price including quantity discount, shipping fees, and estimated delivery date for a customization, plus the key qualifier 'sans rien enregistrer'. That implicitly separates it from the create_* siblings, but no sibling is named explicitly, so it stops short of a 5.

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 only guidance is the conditional 'Donner postal_code pour la date', which tells the agent how to unlock the delivery estimate but not when to prefer this tool over create_design, create_group_order or list_products. Use context (e.g. quote before ordering) is left to inference.

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