create_customer

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

With no annotations, the description should disclose behavioral traits. It only states 'Create a new customer', which implies a mutation, but fails to mention idempotency, duplicate handling, success response, or error conditions. The description is too sparse for a mutation tool with 15 parameters.

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 extremely concise (one sentence, 12 words) and front-loads the action. However, it could be slightly expanded to include basic behavioral information without being verbose, so not quite a 5.

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 tool has 15 parameters and no output schema or annotations, the description is incomplete. It does not explain return values, error handling, or any side effects. The sibling tools offer similar create operations, but this description doesn't provide enough context for an agent to fully understand the tool's behavior.

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 already covers all 15 parameters with descriptions (100% coverage). The description adds no extra meaning beyond stating that only fullname is required, which is also evident from the schema's required array. Baseline is 3 as per guidance.

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 the specific verb 'Create' and resource 'customer', clearly indicating the action and resource. It also states that only fullname is required, distinguishing it from update_customer or get_customer.

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 gives guidance on required (fullname) vs optional fields, but does not specify when to use this tool versus alternatives or prerequisites. It provides basic guidance but lacks context on when to choose create over other operations.

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