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

With no annotations, the description carries the full burden and does so richly: provenance of addresses (brand's own store page, never a homepage or third party), coordSource corroboration, three brands publishing wrong schema.org geo, a hard 'no hours' constraint with instructions never to claim open/closed, a fallback to `phone`, and a result cap of 8. This is exactly the behavioral context an agent needs.

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 verb, resource, and coverage counts before any caveats. The provenance and hours passages are long but each prevents a concrete failure (hallucinated addresses, fabricated opening hours), so they earn their place; the text could still be tightened slightly.

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?

No output schema and no annotations, so the description must cover returns and limits — it states 'Returns up to 8' and the no-argument fallback. For a 3-parameter lookup tool it leaves no material gap an agent would need before invoking it.

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 67%, and the description adds real meaning: `query` 'reads the name, the brand, the category and the one-line `what` the guide keeps', confirming fuzzy multi-field matching beyond the schema's example list. It also documents the no-argument behavior (returns categories and towns), which is parameter-adjacent semantics the schema cannot express.

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?

States a specific resource (verified East End shops) with concrete scope — 74 stores across 9 hamlets on the South Fork, North Fork and Shelter Island — and enumerates the covered categories. It also explicitly distinguishes itself from the sibling `search_places`, so an agent can route without opening a 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?

Gives explicit trigger vocabulary ('any shop, shopping, store, boutique, browse, bookshop, gift or where-can-I-buy question') and a second use case ('the shopping half of a day plan'). It also names the condition that excludes it from a sibling: shops lack hours, which is why `search_places` is used instead.

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