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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior beyond that: the required-parameter combination and, notably, that an unresolvable search or an empty radius yields a well-formed empty result rather than an error — an important non-obvious trait.

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 tight sentences, front-loaded with the tool's identity before the mode/constraint and error-behavior details. Little waste, though the store-contents enumeration in sentence one is slightly listy.

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 document return values, and it correctly focuses on the required-input constraint and empty-result behavior. The only gap is the unexplained radius parameter, which keeps it short of complete.

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 description carries the burden. It explains the semantics of `search` (free-text zip/place) and `lat`/`lng` and their required pairing, but says nothing about `radius_meters` units, default, or accepted range, leaving one of four parameters undocumented.

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 names a specific verb and resource ('H&M physical retail store locator: find nearby stores') and distinguishes itself from the sibling hm_product/hm_search tools by scoping to physical stores. An agent can tell what it returns (store name, phone, address, coordinates) 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?

It clearly states the two supported modes (free-text zip/place search, or direct lat/lng) and the calling constraint that either a search or both lat and lng is required. It does not name alternative siblings or when-not-to-use conditions, so it falls short of a full 5.

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