Ofertas vigentes

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

With no annotations provided, the description carries the full burden. It discloses the discontinued primeOnly behavior and the actionable error, explains the price semantics, and clarifies filter scope. It does not mention pagination or response format, but the core behavioral traits are well-covered for a list tool.

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 three sentences, each adding critical information: the core function and price definitions, filtering options and sibling pointer, and the discontinued flag. There is no redundancy or filler, and the most important details are front-loaded.

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 there is no output schema and no annotations, the description covers the essential context: what an offer is, how to filter, which store is unsupported, and the deprecated parameter. It lacks explicit guidance on default behavior when branchId is omitted, but that is minor since the schema marks it optional. The description is sufficiently complete for an agent to select and invoke the tool correctly.

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%, so the baseline is 3. The description goes beyond by providing concrete examples for category ('Despensa', 'Lácteos'), branchId ('jumboclj512'), and clarifying that primeOnly returns an error. It adds semantic value to the parameters, making the schema more actionable.

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 lists current supermarket offers, distinguishing between discounted price (`price`) and normal price (`listPrice`). It explicitly differentiates from sibling tools by noting that exact member pricing is obtained via get_product (`memberPrice`), and it clarifies the scope and filtering options. This is a specific verb+resource combination that stands apart from other tools.

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 explicit guidance: it names get_product as the alternative for member pricing, warns that primeOnly is discontinued, and notes that Santa Isabel has no offers collection yet. This tells the agent when to use this tool and when to use another, with concrete exclusions and alternatives.

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