create_customer

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

No annotations are provided, so the description must disclose behavioral traits. It states that the tool creates a customer, which implies a write operation, but provides no additional context such as idempotency behavior, duplicate handling, validation rules beyond the schema, permissions required, or what the response contains. This is minimal coverage.

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 a single concise sentence that conveys the essential purpose. It is front-loaded with the action and resource, with no filler or redundant information.

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?

Despite being a simple create tool, there is no output schema and no annotations. The description does not mention return value, success/failure indicators, or any side effects. For a mutation with 100% schema coverage, this is still inadequate because the agent would not know what to expect after invocation.

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 100%, with every parameter having a brief description in the schema. The description does not add any parameter-level detail, but the baseline is 3 because the schema already documents the parameters. It does not, however, clarify the required nature of email beyond the schema's 'required' field.

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 clearly states the action ('Create') and the resource ('a new customer in the Shopify store'). This distinguishes it from sibling tools like update_customer, get_customer, and delete_customer, which perform different operations on the same resource.

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 usage for creating customers but does not explicitly state when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or relationships to tools like create_customer_address. The intent is clear from the name and verb, but no direct guidance is given.

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