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

With no annotations, the description carries the full burden and does well: it discloses the return contents of both reports (product counts, pricing, inventory, SEO, optional sales data) and clarifies the SEO field mapping to Shopify metafields. It does not state the read-only/safety profile, auth needs, or rate behavior, leaving those gaps.

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?

Front-loaded with the core purpose, then the report breakdown, then the SEO mapping, then usage examples. Dense but every sentence carries information; nothing is redundant.

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?

A 7-parameter, dual-report tool with no output schema is well covered: both report modes, SEO semantics, and usage triggers are documented. Minor gaps remain around pagination behavior (only in schema) and permissions, so not quite exhaustive.

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 the baseline is 3, but the description adds real meaning by explaining what each report enum value returns and by clarifying that seoTitle/seoDescription map to Shopify's global.title_tag/global.description_tag. It also implies which parameters apply to the products report (sales data dates, collectionId/collectionTitle), adding cross-parameter context 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?

States a specific verb (Get) and resource (product collections and their contents), then enumerates the two report modes so the agent knows exactly what the tool returns. It is distinguishable from catalog-oriented siblings like get_product_catalog and get_top_products because it centers on collections and their membership.

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?

Gives concrete triggering queries ('how many products in the sandals collection?', 'what products are in collection X?') and ties each to the relevant report type, which effectively tells the agent when to pick list vs products. It stops short of naming an explicit alternative sibling or a when-not-to-use case, so it is clear context rather than full routing guidance.

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