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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, covering the safety profile of this read operation. The description adds that it surfaces unpublished-changes status, which is useful behavioral context, but says nothing about pagination or ordering. With annotations carrying safety, a 3 is appropriate.

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 tight sentences with no waste, and the resource scope plus returned fields are front-loaded ahead of the usage hint. Every clause earns its place.

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 no parameters and no output schema, the description compensates well by listing the fields returned and framing the tool as a discovery starting point. It is nearly complete; only ordering/pagination behavior is left unspecified, which is minor for a no-arg list tool.

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?

The tool takes zero parameters, so the baseline is 4 – there is no parameter syntax the description needs to explain. The description instead documents the output shape, which is beyond the schema's obligations.

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 ('this shop's pages and templates'), then enumerates the returned fields (handle, title, is-template, has-unpublished-changes). This distinguishes it from the singular sibling get_page. An agent can immediately tell what it does and what it yields.

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?

'Start here to find out what exists' clearly signals this as a discovery entry point, establishing context for when to reach for it. It stops short of naming an explicit alternative (e.g., get_page for a single page) or exclusions, so it is strong but not fully explicit routing.

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