Ajouter plusieurs produits

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

Goes well beyond the annotations by disclosing partial-failure behavior ("Un échec n'arrête pas les suivants"), the one exception (a Leclerc Drive block), additive rather than replacing semantics, per-item ordering, and what is returned (each add's result plus the final cart). For a non-idempotent mutation tool this is exactly the operational context an agent needs.

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?

A single tight sentence carries the batch limit, insertion order, additive semantics, failure policy and return shape with no filler. The most decision-relevant facts (batch, cap, additive) are front-loaded.

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?

Covers failure handling, batching and return shape for a non-idempotent mutation with annotations present and no output schema, which is most of what an agent needs. The remaining gap is that it never mentions the store-selection prerequisite implied by the set_store/get_store siblings.

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 coverage is 100%, so product_id, quantity, minItems/maxItems and the 30-item cap are already documented in the schema. The description only reinforces ordering and the cap, adding little parameter-level meaning beyond the schema, so the baseline 3 applies.

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 a precise verb+resource pair ("Ajoute plusieurs produits au panier") with the batch semantics and a hard cap (30 au plus) up front. That verb and the "plusieurs" scope distinguish it cleanly from the single-item sibling add_to_cart without having to open either schema.

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 additive semantics ("chacun en plus de ce qui est déjà au panier") and the batch cap imply when this tool is the right choice for bulk adds. However, it never explicitly says to use add_to_cart for a single item, nor does it state prerequisites such as selecting a store (set_store) before adding.

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