shopify_list_pages

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description reinforces that effect must be 'read' and mentions Spring verification, adding a small operational detail, but it does not disclose pagination behavior, data freshness, or auth handling. The approval_ref note about 'resuming a write' is slightly confusing for a read-only tool but does not directly contradict the 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 description is front-loaded with the purpose and return shape, followed by a compact parameter list. There is minimal filler, though some parameter glosses read as generic boilerplate.

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?

Given that an output schema exists and all parameters are described, the essential call contract is covered. Missing usage differentiation from sibling tools and lack of pagination details beyond the limit parameter keep this 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?

The input schema has 0% description coverage, so the description carries the full burden, and it manually explains all 8 parameters. It adds useful specifics such as the limit range, a query example, and the role of effect, though some generic fields like project_ref and connector_account_ref are only vaguely glossed.

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 first sentence clearly states the operation: 'List Online Store content pages', and the return shape is summarized. It is specific and unambiguous, but it does not explicitly differentiate from nearby sibling tools such as shopify_get_page or other Shopify list tools.

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?

No when-to-use, when-not-to-use, or alternative tool guidance is provided. The intended use is only implied by the verb 'List' and the limit/query parameters, so an agent gets little help deciding between this and similar list/read tools.

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