In-person stores

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low. The description adds real value beyond them: shelf prices are shop-set and can be stale, with the `price_updated` field as the staleness marker, and that city filtering happens server-side on Torob.

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?

Front-loaded with the resource definition first, then the usage trigger, then the tool routing. Three tight blocks with no filler; the parenthetical field list is dense but earns its place as a return-value preview.

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?

With no output schema, the description carries the burden and does so: it lists the returned fields (address, hours, open-now, shelf price and age) and discloses the price-staleness caveat. Nothing an agent needs to call or interpret this tool is missing.

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, but the description adds meaning the schema does not: `city` narrows results server-side to a single city, and `price_updated` contextualizes the returned price age. This is genuine incremental semantic value over the schema text.

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?

Names the specific resource ('in-person (offline) shops that stock a product') and enumerates the payload fields, giving an agent a precise picture of what it returns. It explicitly separates itself from tb_sellers for online offers and from the shop-lookup siblings.

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?

Gives a concrete user-intent trigger ('can I buy it today near me') and names the alternative tool (tb_sellers) for online offers, plus notes the city scoping behavior. It lacks an explicit 'do not use when' beyond the online/offline split, but the routing is clear.

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