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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it hits a 'public' /collections.json endpoint and returns 'normalized' data, which hints at no-auth access and a cleaned output shape, but says nothing about pagination behavior, rate limits, or failure modes for non-Shopify URLs.

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?

A single efficient sentence with zero filler, and the verb and resource are front-loaded. It is arguably too terse for a tool with sibling ambiguity, but there is no wasted wording.

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?

An output schema exists, so return values need not be described, and parameters are fully covered by the schema. What is missing is context tying this generic URL-driven tool to its siblings and confirming the 'collections' vs 'products' distinction, leaving the definition only minimally sufficient.

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 url, page, and limit are already fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Returns') and resource ('normalized collections') and names the exact source endpoint (/collections.json), so the agent knows it lists collections rather than products. It doesn't explicitly contrast with siblings like shopify_collection_products or shopify_products, but the resource noun is distinctive enough to tell them apart.

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?

There is no guidance on when to use this versus the many sibling collection tools (shopify_collection_products, brand-specific *_collections tools) or any prerequisite beyond what the schema states. The description only asserts what it returns, leaving the agent to infer the use case.

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