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

Adds substantial context beyond annotations: no customer number means Collmex assigns the next number, existing customers are never overwritten, each call creates a new record, no message is sent to the customer, and the new customer number is returned. These details are consistent with the non-destructive, non-idempotent annotations.

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?

Four short sentences, front-loaded with the write/create intent, then key constraints, duplicate warning, and return value. Every sentence earns its place with no redundancy.

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?

Covers the write nature, required business fields, duplicate-avoidance workflow, assignment behavior, and return value. Although no output schema exists, the description states the return value directly, leaving no critical gap for correct invocation.

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 coverage is 100%, so the schema already documents all 18 parameters. The description adds a meaningful business rule not encoded in the schema's required fields: at least a company or last name must be supplied. It also clarifies that no customer number is passed, but most parameter meaning remains schema-driven.

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 (create), resource (customer), scope (NEW, record CMXKND), and explicitly distinguishes it from updating an existing customer. An agent can immediately tell this is a creation tool, not a read or update tool.

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?

Explicitly instructs checking collmex_list_customers first to avoid duplicates, warns that each call creates another customer, and states the minimum business requirement (company or last name). This gives clear when-to-use and duplicate-avoidance guidance.

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