Aggiungi al carrello Amazon

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

With no annotations provided, the description carries the full burden. It correctly identifies the operation as modifying and clarifies that no purchase occurs, but it omits critical details such as session/login requirements, behavior when the ASIN is already in the cart, quantity handling, or potential failure modes.

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 consists of two short, focused sentences. It is front-loaded with the core action and includes a clarifying note about the action's scope, with no unnecessary words.

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 a mutation tool with no annotations, no output schema, and minimal parameter explanation, the description is too sparse. It leaves unanswered important questions about prerequisites (e.g., session), quantity semantics, and likely side effects, which are necessary for safe and correct invocation.

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?

The schema defines 'asin' and 'quantity' with pattern and range constraints, but the description adds no explanatory value. Since schema coverage is 0%, the description should compensate by explaining parameter meaning or edge cases, which it does not.

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's function: adding an ASIN to the real Amazon cart. It uses a specific verb and resource, and it distinguishes itself from sibling tools like amazon_remove_from_cart and amazon_get_cart by focusing on the add action.

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 implies usage (adding items to a cart) and notes that it is a modifying action without making purchases, which gives some contextual boundary. However, it does not explicitly specify when to use this tool versus alternatives like amazon_update_quantity or amazon_remove_from_cart.

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