cart_add_with_retry

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

The description discloses the retry mechanism and the condition for correction (initial failure due to ID format issues and auto_correct_ids=True). Annotations already indicate destructiveHint=true, so the description adds value by explaining the automatic correction behavior. However, it does not specify what happens if the retry fails or other side effects.

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 concise, front-loading the core function in the first sentence. It avoids unnecessary detail while covering the essential behavior. There is slight redundancy in retry explanation, but overall efficient.

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 existence of an output schema and full parameter descriptions, the tool description adequately covers the unique retry behavior. It relates to sibling tool cart_add and explains when the correction happens. It does not mention prerequisites like cart existence, but this is acceptable for a tool with clear context.

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 100%, so each parameter already has a description. The tool description adds context for the auto_correct_ids parameter and overall retry logic, but does not significantly enhance understanding of individual parameter semantics beyond the 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?

The description clearly states 'Add item to cart with automatic ID correction', specifying the verb (add) and resource (cart item). It distinguishes itself from sibling tools like cart_add and cart_add_many by highlighting the retry/correction feature.

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 that this tool is a more resilient version of cart_add that recovers from incorrect ID formats when auto_correct_ids=True. Although it doesn't explicitly state when not to use it, the context of automatic ID correction provides clear guidance for when this tool is appropriate.

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