Oportunidades del momento

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

No annotations provided, so the description carries full burden. It discloses return fields, sorting, filtering, and availability on Jumbo. It does not mention side effects, but it is clearly a read operation. The description is transparent about what the tool does.

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 a single, well-structured paragraph of about 6 sentences. It front-loads the core purpose and ordering, then lists return fields, filtering, and specific usage hints. No superfluous information.

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 no output schema, the description lists return fields explicitly. It covers filtering, exclusion, primeOnly, store availability, and limit. It does not mention pagination beyond the limit parameter or error handling, but for a top-deals tool, the information is sufficient.

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 the description adds significant context beyond schema descriptions. For example, excludeIds is explained as 'lo que el usuario ya tiene en el carro o compra siempre', and minDiscountPct includes an example. The description also lists return fields not in 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 explicitly states it returns products with the highest discount and real stock, sorted by discount percentage, for recommending deals. It lists returned fields (discountPct, saving, memberSaving) and filtering options. The title 'Oportunidades del momento' reinforces a clear purpose.

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 clear context: use for finding best deals, with specific usage tips for excludeIds (to exclude user's current items) and primeOnly (exclusive offers). It implies when to use (for deals) but does not explicitly differentiate from sibling tools like get_offers. Nonetheless, the context is sufficient for an agent.

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