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

The readOnlyHint annotation already covers the safety profile, so the description earns credit for what it adds: a concrete disclosure of the returned content domains (ownership, delivery, policies, ordering). With no output schema, this enumeration is the only signal of what an agent gets back.

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?

A single front-loaded sentence with a colon-delimited content list and zero filler. Nothing could be removed without losing 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?

For a no-required-parameter, read-only info tool with no output schema, listing the returned content areas is close to sufficient. Slightly more context on whether the data is merchant-static vs. request-scoped would close the remaining gap.

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?

There is a single optional 'meta' parameter, fully documented in the schema (100% coverage), including its example shape and the note that it is optional here. The description adds nothing about it, which is acceptable given the schema does the work — 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?

The description enumerates precisely what the tool returns: store ownership, delivery options and prices, policies, and ordering mechanics. That clearly separates it from the product/catalog/checkout siblings. It lacks an explicit verb ('get returns...'), but the resource is unambiguous.

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?

There is no statement of when to call this versus alternatives such as lookup_catalog or get_product, and no prerequisites or exclusions. The only hint is the mention of 'how ordering works', which implies pre-checkout context but is not framed as guidance.

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