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

Annotations already flag destructiveHint=true, so the write nature is covered structurally. The description adds value by stating the server assigns the customer number (so the agent should not supply it) and that it is a POST, but says nothing about permissions, idempotency, duplicate handling, or what is returned.

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 fragments, front-loaded with the write marker and the key behavior (server-assigned number). The trailing endpoint string is mild implementation detail but harmless.

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 doesn't state what a successful call returns (e.g., new customer id) or note that most fields are optional. Schema coverage compensates for field meaning, but the response contract is unaddressed.

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% across all 31 parameters, so the schema carries the documentation burden and the baseline of 3 applies. The description itself contributes no parameter-level detail beyond noting the customer number is server-assigned.

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 gives a specific verb and resource ('create a new customer') and adds that Kickserv assigns the customer number. It is clearly distinct from sibling tools like kickserv_create_job or kickserv_update_customer, though it never explicitly contrasts itself with any of them.

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 alternatives such as kickserv_update_customer (for existing records) or kickserv_get_customer. No prerequisites, no mention that only 'name' is required.

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