Shopify Remote MCP Server

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: public (non-authenticated) storefronts, limit up to 250, page-based pagination, and an enumeration of returned fields. It omits rate-limit and error/empty-result behavior, which keeps it below 5.

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, front-loaded with the core action, then return shape, then usage routing — every sentence earns its place. The opening heading line 'Get Shopify Store Collections' is mild duplication of the title, which keeps it from a 5.

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?

There is no output schema, so the description's enumeration of returned fields (id, title, handle, description, image, timestamps) is important and present, as is pagination and limit behavior. Rate limits, auth assumptions, and failure modes are absent, but for a read-only listing tool with annotations the definition is nearly 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 documented with examples and ranges. The description only clarifies that the storefront must be public, which is marginal added meaning. Baseline 3 applies when the schema carries the parameter burden.

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 and resource ('Lists collections from any public Shopify storefront URL') and scopes the domain ('public storefront'). It explicitly names the sibling product endpoint as the downstream consumer of the handles it returns, so an agent can distinguish the two tools without reading either schema.

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 concrete when-to-use context: enumerating category-specific catalogs via the Products endpoint, mapping a competitor's merchandising taxonomy, and tracking collection changes over time. It does not state when *not* to use this tool or what conditions would favor an alternative for the same task, so it stops short of a 5.

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

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: pagination, a limit cap of 250, and an itemized list of returned fields (variants with prices/SKUs/inventory status, timestamps), which matters because no output schema exists.

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, front-loaded with the core action and scope, and each sentence contributes (scope, return shape, use cases). The scenario list is slightly long but no sentence is wasted.

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 read-only list tool with no output schema, the description compensates well by describing the returned fields, pagination and limit cap, and by listing use cases. Nothing critical to correct invocation appears to be missing.

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 schema already documents url, page, limit and collection. The description reinforces limit (up to 250) and collection filtering but adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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/Pulls) and resource (Shopify Store Products) and clearly scopes it to 'any public Shopify storefront URL' with optional collection filtering. An agent can distinguish it from the sibling hasdata_shopify_collections_getCollections (products vs collections) without opening either schema.

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?

The closing sentence enumerates concrete scenarios (price monitoring, catalog mirroring, availability tracking, SKU datasets) that tell the agent when this tool is appropriate. It stops short of naming alternatives or exclusion conditions, so it is clear context without explicit when-not guidance.

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