Create Wave customer

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

Annotations already declare the safe-write profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), so the bar is lower. The description still adds real context beyond them: the write targets the pinned business, duplicate creation is a live risk, and currency overrides business defaults. It does not say what happens if a duplicate is actually submitted, which is the remaining gap.

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 sentences, zero filler, front-loaded with the action and scope before the operational caveats. Every sentence earns its 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?

With an output schema present, return values need not be explained, and the description covers the two operational hazards an agent would realistically hit (duplicates, currency). Adequate for an 8-param create tool with nested address objects and one required field.

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 75%, so the schema carries most parameter meaning already. The description enriches only `currency` (use it for clients billed outside the business default, e.g. USD for US clients); email, phone, address, first_name/last_name and internal_notes are left entirely to the schema. Above-baseline but narrow.

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+resource ('Create a customer') and scopes it to the pinned Wave business, which distinguishes it from wave_update_customer, wave_get_customer, and wave_list_customers. An agent can select it without opening any schema.

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?

Gives concrete pre-call guidance: check wave_list_customers first to avoid duplicates, and set currency when the client is billed in a non-default currency. Names the sibling to consult, but does not state when NOT to use this tool (e.g. prefer wave_update_customer for existing records).

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