Agregar al carro

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

With no annotations, the description provides rich behavioral context: server doesn't handle credentials, returns browserSnippet for manual execution, reversible action, and it is not a purchase. This fully discloses the interactive nature and safety profile.

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?

Description is moderately long (~4 sentences) but each sentence adds value. Front-loaded with purpose. Could be slightly tighter, but not overly verbose.

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?

Despite no output schema, the description explains the outcome (normalized cart with total, ahorro, ahorro Prime) and covers prerequisites, behavior, and reversibility. Complete for a tool requiring external execution step.

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%, and description adds meaning beyond schema: explains rawCartResult's role in normalization and the browserSnippet workflow, which clarifies the parameters' purpose.

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 states 'Agrega/actualiza productos en el carro de Jumbo del usuario', which is a specific verb+resource. It clearly distinguishes from siblings like get_cart that only retrieve cart data.

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?

No explicit guidance on when to use this tool vs alternatives. It mentions prerequisites (logged-in browser tab) but does not compare to other tools or state when not to use it.

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