Agregar al carro

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

With no annotations, the description carries full responsibility. It covers critical behaviors: the server does not handle credentials, the need for a logged-in browser tab, the two-step process, and that the action is reversible and not a purchase. This fully discloses the tool's behavior.

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 relatively concise while conveying necessary steps and prerequisites. It is front-loaded with the main purpose. Minor redundancy (e.g., mentioning reversal twice) could be trimmed, 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?

The tool is complex with a two-step flow. The description adequately explains the prerequisites (logged-in tab), the process (browserSnippet, rawCartResult), and the outcome (normalized cart or snippet). Given no output schema, it sufficiently describes return values. It could mention error handling, but still comprehensive.

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%, providing a baseline of 3. The description adds value by explaining that skuId should use the 'id' field from search_products, that branchId is required, and that rawCartResult is the JSON response from PATCH/GET /cart. This goes 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 the tool adds/updates products in the user's Jumbo cart. It uses specific verbs ('Agrega/actualiza') and resource ('productos en el carro de Jumbo'), distinguishes it from sibling tools like get_cart by noting it modifies the cart, and clarifies it is not a purchase.

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 it (to add/update products) and provides essential context: the two-step flow (returns browserSnippet requiring a logged-in tab), the role of rawCartResult, and that the action is reversible. It does not explicitly mention alternatives or when not to use, but the context is clear.

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