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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=true), and the description adds real value on top: it discloses the Cotlet API key/auth requirement, that missing required fields surface ERPNext's own error, and that no confirmation is asked because the record reaches no one and can be deleted. That is meaningful behavioral context beyond the structured hints.

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 content is front-loaded with the verb and fields, but the first two sentences restate the same fact ('Creates a customer with type, group and territory' / 'Creates a Customer and returns its ID'), which is redundant padding. The remaining sentences earn their place.

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 create tool with no output schema and no nested objects, the description covers the essentials: what is created, what is returned, auth requirements, error behavior for missing required fields, and where address/contact live. Only the explicit alternative-tool routing is absent.

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 the schema already documents all five parameters with their own descriptions. The description reinforces which fields the ERPNext form expects and the required-vs-optional behavior, but adds no syntax or format detail the schema lacks. Baseline 3 applies.

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 opens with a specific verb+resource ('Creates a customer') and enumerates the key fields (type, group, territory), plus the return value (its ID). It is clearly distinguishable from read-oriented siblings like erpnext_list_customers, though it never names a sibling explicitly.

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?

'Pass the ones your site needs' and 'the call returns ERPNext's own error if a required one is missing' give some practical invocation guidance, and it routes address/contact work elsewhere. However, there is no explicit when-to-use-vs-alternatives statement and no prerequisite framing beyond the API key mention.

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