delete_customer

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It discloses the mutation behavior (delete), the constraint (only customers without invoices), and the recommended workflow. While it could mention irreversibility, the delete semantics plus the invoice restriction provide solid transparency.

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?

Efficient 4-line description with a clean structure: purpose statement, exclusions, workflow hint, and parameter example. The Args section adds marginal value since there's only one parameter and it's simple, but the example is genuinely useful for format.

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?

Has an output schema and only 1 parameter, so completeness burden is moderate. The description covers the core behavioral constraint (no invoices) and prerequisite workflow. It lacks details on error messages/return behavior, but for a delete operation with one clear precondition, this is reasonably complete.

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 description coverage is 0%, so the description must compensate. It documents customer_id with an example format ('000001'), which is useful but minimal addition beyond the schema's string type. No additional semantics about uniqueness, lookup behavior, or validation rules are provided.

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 'Delete a customer with no invoices' using a specific verb+resource combination. It distinguishes itself from siblings like update_customer and create_customer by specifying the delete operation and the critical precondition (no invoices).

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?

Provides explicit exclusions: 'Customers with any invoices (posted or unposted) cannot be deleted' and actionable guidance: 'Delete the invoices first, then delete the customer.' This tells the agent when it can and cannot use this tool versus alternatives.

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