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

Annotations only supply destructiveHint=true and a title, so the description's note that CustomerCode must be unique and cannot be changed later is genuinely useful behavioral context. However, it stops there: no mention of required permissions, duplicate-handling behavior, or what happens on a code collision.

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 brief sentences, front-loaded with the action and followed by the one non-obvious constraint. Nothing is padded, though the trailing "Unleashed: POST /Customers" line is endpoint trivia with marginal value to an agent.

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 12-parameter mutation tool with no output schema, the description omits what a successful call returns (e.g., the created customer identifier) and any error/duplicate semantics. The uniqueness warning partially covers the riskiest aspect, leaving it adequate but not complete.

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 12 parameters, so the schema already carries the heavy lifting and the baseline is 3. The description restates the customerCode immutability rule that the schema already states, adding no new parameter-level meaning.

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 the name plus endpoint line make it trivially separable from siblings like unleashed_create_product or unleashed_create_sales_order. It does not explicitly compare itself to any sibling, but differentiation is unambiguous.

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 unleashed_get_customer or unleashed_list_customers, nor any prerequisite such as required lookup of existing codes or duplicate-checking workflow. The only implied usage is the name itself.

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