Get Shopify Pages

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds only a scope statement, and 'List all store pages' is arguably misleading since the schema's default limit of 10 means not all pages are returned; pagination behavior is never 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?

One short, front-loaded sentence with no filler. It is appropriately compact for a simple list tool, though it is arguably too terse to be fully useful.

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 tool, the description still omits key invocation context: no pagination guidance despite a default limit of 10, no indication of what fields a page contains, and no output-schema support since none exists. An agent could call it, but not confidently predict the result set.

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 0%, so the description must carry parameter meaning. It covers the searchTitle concept qualitatively ('search by title') but says nothing about the limit parameter, its default of 10, or its maximum of 250.

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 all store pages') and names the second mode ('search by title'). It implicitly distinguishes itself from the sibling shopify_get_page_by_id (single page) and shopify_update_page (mutation), though it never names those alternatives explicitly.

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 'or search by title' clause hints at two modes, but there is no guidance on when to list vs. search, when to prefer shopify_get_page_by_id, or what pagination/limit assumptions apply. Usage must be inferred entirely.

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