Add to cart

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

Discloses key behaviors: increases quantity if already present, returns updated cart with total. No annotations provided, so description carries full burden. Lacks statement on mutation (e.g., modifies real data) but implies it.

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 sentences, front-loaded with purpose, no filler. Every sentence adds value.

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?

Sufficient for a simple add-to-cart tool. No output schema, but description states what is returned. All necessary information covered.

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 covers both parameters, description adds value by explaining how to obtain product_id and default quantity. Provides context beyond schema.

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?

Clearly states the action (add product to real cart), identifies the source of product ID, and distinguishes from sibling tools like remove_from_cart and set_quantity.

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?

Provides explicit preconditions: get the product ID from search_products or get_my_regulars. Also explains behavior when product is already present. Could be more explicit about when not to use, but sibling tools cover alternatives.

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