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

Annotations declare destructiveHint=true, so the safety profile is partly structured. The description adds two genuinely useful behavioral facts: it is a write, and the customer number is server-assigned rather than caller-supplied. It says nothing about required permissions, duplicate handling, or what the response contains.

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?

Three short sentences with the WRITE flag front-loaded, so the critical mutation signal comes first. The trailing 'POST /{account}/customers.xml' endpoint detail is mildly redundant for an agent but not wasteful.

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 31-parameter creation tool with no output schema, the description is thin: it does not note that only name is required, does not mention that the new customer's identifier is returned, and does not address the destructiveHint annotation. The exhaustive schema carries most of the burden, but the description could do more.

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%, so all 31 fields are already documented in the schema and the baseline is 3. The description adds no parameter-level meaning (e.g., that only name is required, or which contact/company fields matter), so it neither helps nor harms.

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?

States a specific verb and resource ('create a new customer') with a clear WRITE marker, so an agent can immediately tell this is the creation counterpart to kickserv_update_customer and kickserv_get_customer. It stops short of explicitly naming which sibling to prefer in ambiguous cases.

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?

There is no guidance on when to use this versus kickserv_update_customer or how it relates to kickserv_list_customers, and no prerequisites are stated. The only contextual hint is that Kickserv assigns the customer number, which is useful but not usage guidance.

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