shopify_update_customer

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

No annotations provided, so description carries full burden. It correctly indicates a mutation ('update') and notes that only provided fields are applied. However, it does not disclose idempotency, side effects, authorization needs, or return data. Basic transparency but lacks depth.

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?

Single sentence with clear front-loading: action and required parameter. No filler or redundant information. Every word is purposeful.

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 mutation tool with 8 parameters, no output schema, and no annotations, the description covers essential information (update, required id, optional fields) but misses details like return value, error handling, or field-specific notes. Adequate for simple use but not comprehensive.

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 has 8 parameters with 0% description coverage. The description only clarifies that 'id' is required and all others are optional, and that only provided fields are updated. It adds no semantics about field formats, constraints, or behavior (e.g., what 'locale' expects, if 'tags' replaces or appends). Insufficient compensation for lack of schema descriptions.

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?

Clearly states the action 'Update a customer' with the specific Shopify API call 'customerUpdate'. Distinguishes from sibling tools like 'shopify_create_customer' and 'shopify_get_customer' by focusing on update. The required 'id' and optional fields are specified.

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?

Explicitly states the requirement for 'id' and that other fields are optional. While it doesn't provide when-not-to-use or alternatives, the context of sibling tools (create, get, search) makes the usage clear. Lacks explicit exclusions but is sufficient for basic guidance.

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