shopify_store

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

No annotations are provided, so the description carries full burden. It reveals the fallback mechanism from vanity domain to a *.myshopify.com domain, and notes that it returns normalized metadata. This is valuable behavioral context beyond the schema.

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?

Two sentences with no wasted words. The main action and key behavior are front-loaded. Every sentence adds important context.

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 single-parameter tool with no output schema, the description provides sufficient information about input, behavior, and fallback. It could include return format details, but without an output schema, the description is reasonably complete.

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% for the single 'url' parameter, baseline 3. The description adds meaning by explaining that the URL is a public storefront, that it resolves to normalized metadata, and describes fallback behavior. This adds value over the schema's simple 'Shopify storefront URL' description.

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 clearly states the tool retrieves Shopify store metadata, specifies it resolves a public storefront URL, and returns normalized metadata from credential-free storefront JSON. It also describes a fallback mechanism, making the purpose very specific.

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 description mentions 'credential-free' and a fallback behavior, implying it is for basic store info without authentication. However, it does not explicitly state when to use this tool versus other Shopify tools (e.g., shopify_product, shopify_products), leaving the agent to infer usage.

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