Execute confirmed Shopify Admin GraphQL mutation

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation behavior is known. The description adds useful context about the one-time token and environment gating, but does not elaborate on side effects or error behavior beyond what annotations imply.

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 two short sentences that front-load the core purpose and immediately follow with the critical prerequisite. Every part is necessary and no irrelevant details are included.

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?

Given the single parameter, sibling tools, and annotations, the description covers the essential workflow and gating requirement. It does not explain response payloads, but this is acceptable given the execution-oriented nature and lack of output schema.

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 only provides format constraints for confirmationToken, but the description explains its meaning as a one-time token from a previously previewed mutation. This adds semantic clarity that compensates for the 0% schema description coverage.

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 uses a specific verb-resource pair: 'Executes a previously previewed mutation' and identifies the one-time confirmation token as the key input. This clearly distinguishes it from the sibling preview mutation and query 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?

The description clearly states that this tool is for executing a mutation that was already previewed, implying that preview_mutation should be used first. It also mentions the SHOPIFY_ENABLE_MUTATIONS=true prerequisite, giving clear context for when the tool is available.

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