Delete Customer

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

Annotations already mark this as destructive and not read-only, but the description adds 'Permanently' and 'irreversible', which clarifies that the deletion cannot be undone. This goes beyond the structured annotations and is valuable behavioral context.

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 concise sentence, front-loaded with the HTTP DELETE endpoint. It includes all essential information without wasted words.

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 strong annotations, the description is nearly complete. It covers what is deleted, that it is permanent, and that it is by ID. However, it does not mention what happens upon success (e.g., response format) or explicitly reference the bulk-delete alternative, which would tighten completeness.

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 has 100% coverage with the id parameter described as 'The ID of the customer to delete.' The description only says 'by ID', adding no extra meaning beyond what the schema already provides. Baseline of 3 is appropriate.

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 tool permanently deletes a single customer by ID, using a specific verb and resource. The phrase 'single customer' distinguishes it from bulk-delete siblings like gorgias_delete_customers.

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 clearly indicates this is for deleting one customer by ID, which implies the use case. However, it does not explicitly mention when not to use it (e.g., for bulk deletion use gorgias_delete_customers) or provide an alternative, so it lacks a full exclusion.

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