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

With no annotations, the description carries the burden of disclosing behavior. It reveals automatic cart creation, support for product variants, and multi-currency/locale support. However, it claims 'batch operations for adding multiple items at once' while the input schema only accepts a single item object, which is misleading. Missing details about side effects or other behaviors.

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-organized with headings and bullet points, front-loading the main purpose. It is somewhat verbose but each section adds value. A few sentences could be trimmed without losing clarity.

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?

The tool has a complex nested schema and no annotations, but the description provides a clear flow and feature list. However, the inaccurate batch claim and lack of detail on what happens when a cart already exists reduce completeness. The output schema exists, but the description doesn't clarify return behavior.

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 0%, so the description should compensate. It mentions 'product variants, quantities, and custom properties', which aligns with variantEntityId, quantity, and selectedOptions. But it doesn't explain the structure or required fields in detail, and the batch claim may mislead parameter usage.

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 the tool adds products and gift certificates to a shopping cart, with automatic cart creation. It distinguishes itself from siblings like remove_item_from_cart and update_cart_item by explicitly mentioning adding items and creating carts.

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 'Use this tool when' list and a flow showing when to call this tool relative to search_products, get_product_details, and create_checkout_url. However, it doesn't explicitly mention when NOT to use it (e.g., versus update_cart_item).

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