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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only; changes nothing' largely repeats structured data rather than adding to it. The one piece of new information is the money-format convention ('integer minor units (cents)'), which is a genuine data-handling hint but of uncertain relevance to store records.

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?

Three short sentences with the resource stated first and no filler. It is efficient, though the money-units sentence is of questionable applicability to a store-listing tool and consumes space that could have carried usage or scoping information.

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 would normally need to explain the return shape, but the input schema's description already enumerates the returned fields (address, map presence, point, hours, tags, pickup availability, locator page address). Combined with annotations covering the safety profile, the definition is close to complete; only routing to the sibling mutation tools 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?

The tool takes zero parameters, so there is nothing for the description to clarify and the baseline is 4. The description neither needs nor provides parameter detail, and the empty input schema is unambiguous.

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 is a bare noun phrase, 'The shop's stores,' which restates the resource identified by the tool name but supplies no action verb (list/retrieve/return). An agent can infer it returns the shop's store list, but the description itself does not state what the tool does or differentiate it from the store_locator_set/store_locator_remove 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?

The only usage signal is 'Read-only; changes nothing,' which implies the tool is safe to call but gives no explicit when-to-use guidance and never names the adjacent store_locator_set or store_locator_remove tools an agent would otherwise consider. No prerequisites or conditions are stated.

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