shopify_collections: GET /

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

No annotations provided, but the description does not disclose any side effects, rate limits, or authentication requirements. It adequately indicates a read operation and public URL requirement.

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?

Three sentences with no fluff; first sentence is a clear title, second describes functionality, third provides usage direction. Excellent structure.

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?

Despite lack of output schema, description details return fields and pagination. The tool's purpose and integration with sibling are fully covered for its complexity.

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%, so schema already documents params. Description adds context (limit up to 250, pagination, public URL) but does not significantly augment semantics beyond schema.

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 the tool lists Shopify collections with pagination, and distinguishes from sibling hasdata_shopify_products_getProducts by mentioning returned handles as input to that endpoint.

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?

Explicitly explains how to use the returned handles with the Shopify Products endpoint and provides use cases like mapping taxonomies. Lacks explicit when-not-to-use instructions but overall strong guidance.

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