Estado del carro

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

Discloses that credentials are not seen by server ('El servidor no ve credenciales') and describes the two modes (normalize or return snippet). Lacks mention of rate limits or other side effects, but for a read-like tool with no annotations, this is above average.

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?

Single paragraph with important information front-loaded (purpose, workflow). Slightly dense due to embedded instructions but efficient overall.

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?

Describes output format explicitly despite no output schema. Addresses the full workflow and integration with browser snippet. With sibling tools, this provides sufficient context for correct usage.

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?

Adds significant meaning beyond the input schema: explains store default and phase, rawCart source from GET /cart, branchId as sucursal. The description clarifies the workflow for each parameter.

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 normalizes the user's Jumbo cart into a specific format (items, subTotal, total, savings, primeSavings). It distinguishes from siblings like add_to_cart and get_product by focusing on cart normalization.

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 when-to-use: 'FLUJO RÁPIDO (una sola llamada)' with browser snippet, and when-not-to: 'NO extraigas el estado de React ni el DOM del carro a mano'. Also explains fallback behavior if rawCart is not provided.

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