create_customer

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: the requirement for email/phone, optional inline address creation, and that the response includes the auto-generated id. It does not discuss error cases or idempotency, but the most important side effects and return behavior are covered.

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 three sentences, front-loaded with the purpose, and contains no redundant information. Every sentence earns its place by adding a constraint, an optional feature, or return behavior.

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 create operation with no output schema and no annotations, the description covers the essential aspects: purpose, required input condition, optional nested feature, and return value. The rich schema for addresses compensates for lack of detail there, though some parameter nuances remain undocumented.

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 only 45%, so the description must add meaning. It does add a critical constraint (email OR phone) that is not reflected in the schema's required fields, and clarifies the addresses array. However, it does not elaborate on most other parameters, leaving significant gaps that the schema only partially fills.

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 begins with 'Create a new customer,' a specific verb and resource that clearly distinguishes it from update_customer and read-only customer tools. It unambiguously states the action and object.

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?

Clear context is provided: this tool is for creating new customers, with a mandatory condition of email or phone. It does not explicitly name alternatives like update_customer, but the context is unambiguous and no exclusions are stated.

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