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

With no annotations provided, the description carries the full burden and does well: it discloses the public-storefront scope, pagination behavior, limit cap of 250, and the specific returned fields. It doesn't mention rate limits or error behavior, but the core behavioral expectations are clear.

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 concise and front-loaded, stating the main function first and then adding return-detail and usage context. The closing sentence about tracking collection changes is slightly extra but still adds practical context.

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 no output schema and no annotations, the description adequately compensates by explaining return fields, pagination, and the public URL requirement. It stops short of covering defaults or error scenarios, but the information needed to invoke the tool correctly is present.

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 100%, so the baseline is 3. The description adds only marginal reinforcement by mentioning 'limit (up to 250) and page pagination,' which the schema already documents. It does not introduce new semantic details beyond the 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 'Lists collections from any public Shopify storefront URL' with a specific verb, resource, and scope. It also lists the returned fields and distinguishes collections from the sibling products endpoint by referring to it as a separate input consumer.

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?

It gives clear context: use this to fetch collection-level data from public Shopify stores and feed handles into the Shopify Products endpoint. It doesn't explicitly say when not to use it, but the workflow guidance makes the intended usage obvious.

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