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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful context beyond that: the source endpoint (/pages.json) and the return format ('page bodies are returned as cleaned text'), which tells the agent the content is normalized rather than raw HTML. Auth/rate-limit behavior is not mentioned.

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, zero waste, and the core purpose is front-loaded ahead of the sibling routing.

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 an output schema carrying the return structure and annotations carrying the safety profile, the description supplies the remaining essentials: what is listed, from where, in what form, and which alternatives to use instead.

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 url, page, and limit are already fully documented with defaults and constraints in the schema. The description only names the three parameters without adding syntax or format meaning, so baseline 3 is appropriate.

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 ('List') and resource ('normalized static-page records from a public Shopify /pages.json endpoint') and explicitly names the two siblings it is not, so an agent can distinguish it from shopify_page and shopify_sitemaps without opening any 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?

Explicitly routes the agent with 'Use shopify_page for one page or shopify_sitemaps for URL discovery', giving clear conditions that select the alternatives. It doesn't spell out when this tool is preferred beyond contrast, but the routing intent is unambiguous.

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