shopify_get_preview_store

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context that the store is temporary and app-created, but it does not clarify what 'refresh' means in terms of output or side effects, which would have added value beyond the annotations.

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?

The description is one short, front-loaded sentence with no filler or redundant wording. It earns its place, though the brevity leaves some important behavioral and parameter details unstated.

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 simple tool with one required parameter and strong annotations, the description is minimally viable: it states the operation and scope. However, with no output schema and no parameter-level guidance, it leaves the return behavior and the exact expected input format unstated, so the agent still has to infer important details.

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?

The schema has 0% description coverage, and the description does not explain the 'store' parameter beyond implying it refers to the temporary store created by the app. This gives some contextual clue, but it does not specify whether the expected value is a store ID, domain, or name, so the parameter meaning remains under-specified.

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 names a specific action ('Refresh preview and claim links') and a specific scope ('temporary store created by this app'), which makes the tool's purpose clear. It distinguishes itself from general store tools, though it does not explicitly contrast with the sibling preview tools like shopify_get_new_store_previews.

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 implies when to use the tool: when a temporary store's preview and claim links need to be refreshed. However, it provides no explicit guidance about when not to use it or which alternative sibling tools to prefer, such as shopify_get_new_store_previews or shopify_get_new_store_preview_status.

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