shopify_update_customer

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

Annotations already declare readOnly=false, destructive=true, idempotent=false, and openWorld=true; the description adds rich context beyond them. It explains the dryRun preview/apply cycle and return shape (current/change vs before/after), clarifies exactly what replaceTags destroys, and names the required write_customers permission. No contradiction with 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?

Four compact sentences front-load the core operation, then cover dryRun behavior, tag semantics, scope, and authorization. Every sentence carries useful information with no filler or repetition, making it easy for an agent to parse quickly.

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?

With no output schema, the description still explains what dryRun:true and dryRun:false return, which covers the agent's need to understand outputs. It also covers authorization, tag behavior, and out-of-scope concerns, leaving only basic schema constraints (id format, store, note/email patterns) to the schema itself, which is appropriate.

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 50%, so the description needs to compensate somewhat. It adds meaning beyond the schema by explaining the interaction between addTags, removeTags, and replaceTags, and by restating dryRun default behavior and its return semantics. It does not cover id or store beyond the required schema constraints, but the tag semantics are the key non-obvious parameters.

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?

States a specific verb (Update), resource (customer), and the exact updatable fields (note, email, tags), while also naming the underlying customerUpdate mutation. This clearly distinguishes it from sibling tools like shopify_update_product or shopify_update_order, so an agent can route correctly without opening 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?

Gives clear context: use this to update note, email, and tags, with a default dryRun preview and explicit tag add/remove/replace semantics. It also states a prerequisite (write_customers) and one scope exclusion (email marketing consent is out of scope). It stops short of naming alternatives, but no sibling tool directly competes for this operation.

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