get_store_offers

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

The annotations already establish readOnlyHint=true, so safety behavior is covered. The description adds useful return-content context not found in structured fields: prices, unit prices, store name, and expiry dates. It falls short of disclosing ordering, pagination beyond the schema limit, or freshness behavior.

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 front-loaded with purpose, then routing guidance, then return contents. Every sentence adds useful information with no repetition or wasted wording.

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?

For a read-only list tool with an annotation covering safety, full schema descriptions, and no output schema, the description supplies the missing return-value context and routing guidance. Nothing needed to invoke it correctly appears absent.

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 both parameters are already documented in the input schema, including the instruction to use list_stores for store lookup. The description adds only the conceptual framing of 'specific store' and no syntax or format details beyond the schema, making the baseline 3 appropriate.

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 states a specific verb and resource: 'List current offers from a specific store.' It also distinguishes the tool from siblings search_deals and deals_this_week, so an agent can identify its exact scope without opening another schema.

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?

It gives explicit USE WHEN and NOT FOR guidance, including a concrete example ('what's at Netto this week') and names the alternative tools for cross-store and preferred-store searches. This leaves no ambiguity about when to select this tool.

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