shopify_create_preview_store

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

Beyond annotations, the description adds meaningful behavioral context: the store is 'real' but 'temporary', 'a merchant can claim' it, and 'No existing store is modified' — which aligns with destructiveHint=false. It also explains idempotency behavior ('Reuse requestId after interruptions to prevent duplicate creation'), going beyond the bare idempotentHint=true annotation.

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 tight sentences: the core purpose is front-loaded, followed by the non-destructive guarantee and the idempotency instruction. Every sentence earns its place and there is no filler.

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 creation tool with 4 params and no output schema, the description covers the essential outcome and safety characteristics. It does not describe the return value, claim process details, or store lifetime, but the action and constraints are sufficiently clear for an agent to invoke it correctly.

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 0%, so the description must compensate. It adds meaning for requestId (reuse for idempotency) but does not explain name, country, or userUnderstandsNewStoreOnly. Those names are largely self-explanatory and schema constraints provide additional detail, but the description could do more to clarify the consent parameter.

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 action ('Create a real temporary Shopify store') and resource ('preview store'), and explicitly differentiates from modifying existing stores. This clearly distinguishes it from sibling getter tools like shopify_get_preview_store and 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 gives clear context: use this to create a temporary, claimable store, and it explicitly says no existing store is modified. It lacks an explicit 'when not to use' or named alternative, but the action is unambiguous and the requestId-reuse guidance provides practical usage direction.

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