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

readOnlyHint=true already establishes the safety profile, so the description's job is lighter; it adds that the response carries shopID, name, time zone, and archived flag, plus the underlying endpoint. It does not say whether archived shops are included by default or describe pagination behavior, but these are minor against the annotation coverage.

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 plus an endpoint reference, front-loaded with the resource and returned fields. The raw "GET /Account/{accountID}/Shop.json" path is mild filler for an agent, but nothing else 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?

For a read-only, zero-parameter-required list tool with full schema coverage and no output schema, the description usefully fills the return-value gap and explains how shopID is consumed elsewhere. The one residual ambiguity — whether archived shops appear by default — keeps it from being fully 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 coverage is 100%, so sort, limit, next_url, and include_contact are already fully documented in the schema. The description adds nothing about parameters — the field list refers to return values, not inputs — which is acceptable but not additive.

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 ("List the account's shops"), clarifies that shops are store locations, and enumerates the fields returned. The resource is unmistakably distinct from the sibling list_* tools for customers, items, sales, vendors, etc.

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 second sentence gives downstream guidance ("Use shopID to filter sales, inventory and purchase orders"), which implies this is a discovery/enumeration step feeding other calls. However, it never states when to use this versus alternatives or any preconditions, leaving usage to inference.

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