create_customer

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

No annotations are supplied, so the description must carry the full behavioral burden. It says that a new customer is created and that displayName is the minimum requirement, but it omits duplicate handling, authentication needs, validation behavior, side effects, and response characteristics.

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 description is two compact sentences, front-loads the action and required field, and contains no filler. Every sentence contributes directly to understanding the operation.

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 a nested object, no annotations, and no output schema, the description is too thin. It covers the minimum viable call but leaves important behavioral, field-level, and integration context 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?

The schema exposes many nested customer fields, but the description adds useful high-level grouping: required display name, optional contact details, billing address, and payment terms. It does not map every optional field or specify formats, so it partially compensates for limited schema-level guidance.

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 states a specific verb and resource: 'Create a new customer in KikoBooks.' It is clear and actionable, though it does not explicitly differentiate from siblings such as update_customer, delete_customer, or promote_deal_to_customer.

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?

The description implies use when creating a new customer and gives the minimum required field, but it does not say when to choose this over update_customer, promote_deal_to_customer, or other creation alternatives. No exclusions or broader workflow context are provided.

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