create_customer

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

Beyond annotations, the description discloses the idempotency guard, duplicate-check refusal behavior, dry_run functionality, and required permissions (CUSTOMERS_R and CUSTOMERS_W). This adds significant behavioral context beyond the basic readOnly/destructive 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 description is concise and structured: a clear action statement, followed by idempotency behavior, dry_run, and permission requirements. Every sentence adds value without unnecessary repetition.

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?

Given the 7 parameters and zero schema descriptions, the description covers the essential non-obvious behaviors (duplicate handling, dry_run, permissions) and relies on the output schema for return format. It is sufficiently complete for effective tool selection and 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?

With 0% schema description coverage, the description compensates by explaining dry_run, confirm_duplicate, and the role of email/phone in the duplicate check. It does not explicitly describe marketing_allowed, but most parameter meanings are clear from their names and defaults.

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 clearly states 'Create a new customer record in Clover', using a specific verb and resource. It distinguishes itself from sibling tools like update_customer by focusing on creation rather than modification.

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 provides clear context that this tool is for creating new customer records, including idempotency guard behavior. However, it does not explicitly mention when to use an alternative like update_customer or list when not to use the tool.

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