delete_customer

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

The description adds behavioral context beyond annotations by flagging the tool as 'DESTRUCTIVE' and including the HTTP DELETE method and endpoint. It also reiterates the destructive nature, which, combined with annotations, gives a clear safety profile.

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 somewhat repetitive, stating 'Delete a customer' multiple times and including the redundant phrase 'Deletes a record.' While it front-loads the destructive warning and HTTP path, the overall length could be reduced without losing clarity.

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 a single parameter and no output schema. The description covers the purpose and usage guidelines but does not mention what the tool returns upon success or failure. Given its simplicity, the description is adequate but could be more complete with a note on return behavior.

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 only parameter 'id' is documented in the schema with a description. The tool's description does not add any additional meaning or context beyond what the schema already provides. Since schema coverage is 100%, a score 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 identifies the action as 'delete' and the target resource as 'e-commerce customer', distinguishing it from other delete tools for different resources. The inclusion of the HTTP method and path further clarifies the specific operation.

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 an explicit instruction to confirm with the user before calling, which is a crucial usage guideline for a destructive operation. While it does not mention alternatives or when not to use, the guidance provided is sufficient for safe invocation.

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