wave_delete_customer

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

The description discloses the precondition for deletion, which is important behavioral context. However, it does not cover other aspects like error handling, reversibility, or required permissions. With no annotations, more detail would be beneficial.

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 a single sentence that conveys the essential information without any noise. It is well front-loaded and efficient.

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 simple delete tool with two parameters and no output schema, the description is largely complete, covering the key precondition. It could be improved by mentioning the response or error behavior, but it is adequate for an agent to use correctly.

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 input schema already provides full descriptions for both parameters (businessId and customerId), so the description does not add additional parameter-level semantics. The condition about invoices is about usage context, not parameter meaning.

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 the verb 'delete' and the resource 'customer', with a specific condition 'only if they have no invoices'. This distinguishes it from sibling tools like wave_delete_invoice and others.

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 includes a clear precondition ('only if they have no invoices') that guides when to use this tool. However, it does not provide explicit guidance on when not to use it or suggest alternative tools for cases where the condition is not met.

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