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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, which cover the safety profile. The description adds value by disclosing the live-store nature ('from the live store') and explaining how returned updatedAt values are consumed in a publish workflow. No contradictions with annotations.

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?

The main listing is front-loaded, but the final 'Routing:' line repeats information already stated in the first sentence (title/handle/published, pages include updatedAt). This redundancy makes the description slightly longer than necessary without adding new 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 simple read-only list tool with only two parameters, the description covers what is returned, when to use it, and the important downstream note about expected_updated_at. Pagination behavior (limit default/max, blogs up to 10) is already covered by the schema. No output schema exists, but the return fields are described inline, so the agent has what it needs to call the tool correctly.

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% – both companyId and limit have descriptive text. The description adds no new parameter-level meaning beyond clarifying which output fields are returned and how updatedAt is used downstream, which doesn't alter the baseline of 3 when the schema already documents the parameters.

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 clearly states it lists the connected Shopify store's online-store pages and blogs, naming the specific fields returned for each (title, handle, published status, updatedAt for pages; title, handle for blogs). This distinguishes it from sibling Shopify list tools like list_shopify_products, list_shopify_orders, and list_shopify_themes by specifying the exact resource type.

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 description explicitly says to use it to see existing site content before drafting a new page or blog post, giving a clear when-to-use context. It also provides a specific downstream workflow note: pass a page's updatedAt as expected_updated_at when proposing a page publish. It does not explicitly name alternative tools or exclusions, but the use case is clear enough for an agent.

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