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 adds genuinely useful behavior beyond that: the returned fields per store (name, address, phone, coordinates, distance, store page URL) and the empty-result semantics when nothing is in radius.

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 tight sentences, front-loaded with the core purpose and the search mechanism, followed by return content and edge-case behavior. Nothing 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?

With an output schema present, the description needn't detail return values, yet it usefully notes the empty-result case. The main gap is the unexplained 'page' parameter and radius units, minor against a locator tool with clear annotations.

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 0%, so the four parameters (lat, lng, page, radius_miles) are undocumented in the schema. The description clarifies that coordinates and radius drive the search, but never maps these to the parameter names, units (miles), or explains pagination via 'page'. Partial compensation only.

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 ('search nearby stores' via a 'Nike physical retail store locator') and the exact scope (coordinates + radius). An agent can distinguish it from nike_search or nike_product immediately.

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 implies when the tool is appropriate (you have coordinates and want nearby Nike stores), but it never names an alternative sibling or a when-not condition. No sibling store-locator exists for Nike, so the gap is modest, but the guidance remains implicit rather than explicit.

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