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 elsewhere. The description adds nothing beyond that: it does not say what "metadata" comprises, what the response looks like, or that arbitrary storefront URLs are fetched. The one behavioral detail in the definition (rejection of localhost/private/link-local/credentialed URLs) lives in the schema, not the description.

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?

Four words that duplicate the tool name with no added information; this is under-specification rather than useful conciseness. Nothing is front-loaded because nothing substantive is present.

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 annotations cover the read-only profile. However, for an open-world fetch tool the description is effectively empty: it does not define scope, expected inputs, or how it relates to the sibling Shopify tools, leaving genuine gaps.

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?

With a single parameter and 100% schema description coverage, the schema already carries the full contract (full storefront URL, http/https, rejection rules), so the baseline of 3 applies. The description adds no additional meaning about the url argument.

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 is a noun phrase, "Shopify store metadata," that essentially restates the tool name shopify_store rather than stating a verb+resource action. It gives no sense of how it differs from the large set of sibling Shopify tools (shopify_product, shopify_products, shopify_page, shopify_collections), so an agent cannot distinguish it from them without inspecting the 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?

There is no when-to-use guidance, no prerequisites, and no named alternative. Nothing tells the agent when to pick shopify_store over shopify_products or shopify_sitemaps, or that the input must be a storefront root URL rather than a product or collection URL.

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