shopify_list_collections

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

With no annotations provided, the description carries the behavioral disclosure burden. 'List' implies a read operation and 'with pagination' signals limited results, but it does not explain how pagination works, whether cursors/pages are used, or what the response contains. This is acceptable for a simple list tool but not rich.

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 a single concise sentence with no filler or redundant information. It front-loads the core action and resource, and every word contributes value.

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 low-complexity tool with one optional parameter, the description is adequate at a high level. However, since there is no output schema, the absence of return-value details or pagination mechanics leaves some ambiguity for an agent deciding whether the response is sufficient for downstream use.

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 0%, but the schema itself is self-explanatory for the single 'limit' parameter, with type, default, and maximum. The description's 'pagination' hints at the limit's purpose, but it does not explicitly describe how the limit controls page size or how consumers should paginate.

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 states a specific verb ('List'), a resource ('collections'), and a behavioral detail ('pagination'), so an agent can tell what the tool operates on. It is clear and distinct from sibling tools, though it does not explicitly scope the listing to 'all collections' or define the collection 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?

Usage is implied by the resource name: use this when you need to list collections, not products, orders, or customers. However, the description provides no explicit when-to-use guidance, exclusions, or mention of an alternative collection-specific tool.

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