create_customer

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

With no annotations, the description carries full burden but only states the action and HTTP mapping. It does not disclose whether permissions are required, what side effects occur (e.g., creation of related records), or the response format. Critical behavioral traits are missing.

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 only two sentences with no fluff, but it is under-informative for a tool with 8 parameters and nested objects. It could be more structured (e.g., listing prerequisites or output) without becoming verbose.

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's complexity (8 parameters, nested objects, no output schema), the description is incomplete. It omits what the tool returns, validation rules, and any distinctions from sibling tools beyond the action.

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 13%, yet the description adds negligible parameter-level meaning beyond noting that location is part of the creation. For the 8 parameters, only location is hinted at; no details on required fields, email, phones, status, etc., are provided.

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), the resource (customer), and includes a specific detail (with a service location) that distinguishes it from update/delete operations. The explicit mapping to POST /customers further clarifies the API endpoint.

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 provides no guidance on when to use this tool versus alternatives like update_customer or add_customer_note. It does not mention prerequisites, such as needing a valid location or that this tool is for new customers only.

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