Productos frecuentes del usuario

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

With no annotations, the description fully discloses that it requires a logged-in session, uses a browser snippet, and warns against scraping React state or improvising selectors. It also states the server never handles credentials, adding important security context.

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 somewhat long but front-loaded with the main purpose. It includes necessary instructions, but some sentences could be more concise.

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 tool's complexity (no output schema, 3 params), the description provides enough context: it explains the output format (normalized prices, DOM-extracted cards), the requirement for a session, and behavioral constraints. It is complete for an agent to use effectively.

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 the schema already explains parameters. The description adds value by explaining that the cards parameter comes from DOM extraction, but does not add significant new meaning beyond 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 it returns frequently purchased products with normalized prices and Jumbo Prime price. It distinguishes itself by being the base for building the user's actual purchase list, differentiating from siblings like get_saved_lists or build_list.

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 provides context that it requires a session and uses a browser snippet, and its purpose is explained. However, it does not explicitly state when to use this tool versus alternatives like get_saved_lists or 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.