cart_add_many

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

Annotations provide destructiveHint: true, indicating mutation. The description adds critical context: strict success semantics (failure of any item does not remove successfully added items) and the confirm parameter for human-in-the-loop safety. No contradiction with annotations.

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 well-structured with clear sections, but slightly verbose. Every sentence provides useful information, though it could be condensed without losing clarity. Overall effective.

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, the description does not need to explain return values in detail, but it summarizes success/failure. It covers parameters, behavior, and usage context, differentiating from sibling tools like cart_add_with_retry. Adequate for the tool's complexity.

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%, and the description adds meaning by specifying that items require product_id, sku_id, and quantity, with a max of 100 items. It also explains that confirm must be True to execute, defaulting to preview. This adds value beyond the schema descriptions.

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 'Add multiple items to cart with a single confirmation,' which is a specific verb and resource. It distinguishes itself from sibling 'cart_add' by emphasizing efficiency and a single confirmation gate.

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 explains when to use this tool (multiple items, efficiency) and mentions the confirmation gate. It implies when not to use it (single items), but lacks explicit exclusions or alternatives beyond the implicit comparison with cart_add.

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