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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful behavior beyond them: the credential-free source, the fallback from a blocked vanity domain to a discovered *.myshopify.com domain, and the URL rejection rules. It doesn't state rate limits or failure modes when neither domain works, keeping it short of a 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?

Front-loads the core purpose, then fallback behavior, then URL constraints, then the alternative tool. Efficient overall, though the url sentence duplicates the schema description verbatim, which is minor redundancy.

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 the description covers the key non-obvious behaviors (fallback, credential-free source, URL validation). Complete enough for an agent to call it correctly, with only minor gaps around failure handling.

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% and the single url parameter is fully documented in the schema. The description repeats the same format, http/https requirement, and rejection rules without adding anything new, so 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 (Resolves) and resource (public Shopify storefront) and the return ('normalized metadata from credential-free storefront JSON'). It also names the sibling shopify_product and clarifies the division of labor, so the agent can distinguish it from the many other shopify_* tools.

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 explicit routing to shopify_product for product data, which is clear context for one alternative. However it offers no guidance on when to prefer it over shopify_products, shopify_collections, or shopify_search_suggest, so the coverage of alternatives is partial.

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