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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real behavioral context beyond that: chains/franchises excluded, results not ranked by commission, and the pilot-area coverage caveat for the directory. It stops short of describing result size/pagination.

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?

Purpose and location format are front-loaded, and most sentences carry unique constraints (radius bounds, exclusions, ranking). It runs long as a single dense block with some comma-heavy enumeration, but little is wasted.

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?

An output schema exists, so return values need not be explained. The description covers location format, category behavior, radius limits, and exclusions, which is nearly everything an agent needs to call it correctly; only result-set behavior (volume/ordering) is unaddressed.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does: location format with concrete examples ('55401' or 'Duluth, MN'), radius_km bounds (0.1 to 500, default 25, shops searched within 15), and category narrowing either list. Category acceptable values remain vague (no enum, only implied by the business-type list).

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 verb (find) and resource (local businesses), and details exactly what is returned: Shoptegrity's directory (co-ops, markets, credit unions) plus independent shops by category across the US. The scope distinction (US ZIP code or town/state) lets an agent differentiate it from brand/deal/alternative siblings without opening the 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 clear usage context ('for Small Business Saturday or any local shopping') and a meaningful exclusion ('Chains and franchises are left out'), which tells the agent when this tool is appropriate. It does not name sibling alternatives or explicit when-not conditions, so it falls short of a 5.

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