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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds real behavioral value by enumerating the returned fields (name, address, phone, coordinates, distance, page URL) and disclosing the edge-case behavior that a radius with no nearby stores returns a well-formed empty result rather than an error.

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?

Two sentences, front-loaded with the core capability and followed by the edge-case guarantee. No filler, nothing repeated from the schema except the minimal framing needed.

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 an output schema present, the description need not explain returns, yet it does so briefly, and it covers the empty-result edge case plus the coordinate/radius contract. Nothing essential for a correct call is missing; only explicit alternative-tool routing is 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 description coverage is 100%, so lat, lng, page, and radius_miles are all documented in the schema itself. The description only restates 'coordinates and radius' without adding format, default, or pagination semantics beyond that, so the baseline 3 applies.

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 and resource ('Nike physical retail store locator: search nearby stores') and names the scoping mechanism (coordinates and radius). It is trivially distinguishable from the sibling product/search/suggest tools in the nike_* family.

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 description makes clear this is the tool for finding physical stores near a coordinate, which implicitly routes an agent away from product-oriented siblings. However, it never explicitly states when not to use it or names an alternative tool, so it stops short of the 5-level routing guidance.

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