Ofertas vigentes

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

With no annotations, the description fully discloses behavior: it lists offers with price fields, supports filtering, and notes that primeOnly returns exclusive offers but exact prices require get_product. It does not mention pagination behavior beyond page/limit or response structure, but for a read-only list tool this is adequate.

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 two sentences: first explains what the tool does and key fields, second covers filtering and the primeOnly nuance. Every word is informative with no fluff, perfectly 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 no output schema, the description explains the key fields (price, listPrice) and filtering capabilities, but does not detail the full return structure, sorting, or error states. It is sufficient for correct invocation but leaves minor gaps for complex queries.

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%, and the description adds business meaning (e.g., price vs listPrice explanation, primeOnly linking to get_product, category examples). It enriches the schema definitions without redundancy.

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 lists active supermarket offers with a price rebate, distinguishing price and listPrice. It mentions filtering by category, branchId, and primeOnly, and references get_product for exact member prices, making the purpose specific and distinct from siblings like get_product.

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 implicit usage context (filtering options) and explicitly notes when to use get_product for exact prime prices. It also warns that santaisabel store currently lacks an offers collection, guiding the agent. However, it does not explicitly state when not to use this tool or compare to other listing tools.

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