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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds that addresses are returned and that ids feed other filters, but it says nothing about pagination, result size, or how show_deleted/soft-deleted records behave, so the added behavioral context is modest.

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 compact sentences plus an endpoint mapping, with the core purpose front-loaded and no filler. Every clause carries information (scope, returned fields, downstream id usage, API path).

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 read-only list tool with six fully documented optional filters and readOnlyHint covering safety, the description is largely sufficient. It does not address pagination or the volume of results, which is a minor gap given there is no output schema.

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 all six filters (store_ids, show_deleted, created/updated min-max) are already documented with format and semantics. The description adds only that store ids are consumed by receipt/shift/inventory filters, which is marginal extra meaning over the schema; baseline 3 is correct.

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+resource ("List the merchant's stores (locations)") and the payload shape ("with their addresses"). It also clarifies that store ids are the key consumed by receipt/shift/inventory filters, which helps distinguish this from the other list_* siblings, though it never names a sibling directly.

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 sentence about store ids being what receipt, shift and inventory filters take implies the main reason to call this tool (resolving store ids for later filtering), but it is implied rather than an explicit when-to-use statement. No alternatives or when-not conditions are given.

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