Delete Customers (Bulk)

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds the critical context that deletion is 'permanent,' which is not explicitly in the annotations. It also specifies the HTTP endpoint 'DELETE /api/customers', providing additional behavioral clarity beyond the structured 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 two sentences long, front-loaded with the HTTP method and purpose, and contains no filler. Every word earns its place by conveying the endpoint, bulk nature, and permanent outcome.

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?

The tool has only one parameter, clear annotations, and no output schema. The description covers the essential aspects: what it does, how it operates (bulk delete via DELETE), and the permanent impact. For a straightforward bulk delete operation, this is complete and sufficient for an agent to select and invoke 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?

Schema coverage is 100% for the only parameter 'ids', and its description 'A list of customer IDs to delete' fully explains the property. The tool description simply restates this without adding extra meaning, so it meets the baseline for high schema coverage but adds no additional value.

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's function: 'Bulk delete multiple customer records' and 'permanently deletes all specified customers.' It uses a specific verb and resource, and the 'Bulk' qualifier distinguishes it from the sibling singular 'gorgias_delete_customer'.

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 implies this is for bulk deletion when multiple customer IDs need to be removed. It doesn't explicitly mention alternatives like 'gorgias_delete_customer' for single deletions, but the title and context provide clear guidance. However, missing explicit exclusions or alternative references keeps it from a 5.

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