delete_customer

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

The description discloses that the operation is destructive, which is crucial for a delete tool. Given the lack of annotations, this adds necessary behavioral context. However, it omits details like irreversibility, required permissions, or whether the action can be undone.

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 extremely concise with only 8 words. It front-loads the action and key trait (destructive). While efficient, it could be slightly more structured by separating the destructive warning into a standalone sentence for emphasis.

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 1-parameter delete tool, the description provides a minimal but sufficient explanation of functionality. The presence of an output schema helps cover return values. However, the description lacks context about side effects or typical use cases.

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 sole parameter 'customer_id' has no description in the schema (0% coverage). The tool description adds no additional meaning beyond the parameter name and title. It does not clarify format, expected length, or how to obtain the ID.

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 deletes a customer and all associated data, which matches the verb 'delete' and resource 'customer'. It is distinct from sibling 'delete_customer_account' by implying cascading deletion, but does not explicitly differentiate.

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?

No explicit guidance on when to use this tool vs alternatives like delete_customer_account. The word 'Destructive' hints at caution but does not advise against misuse or provide context for safe usage.

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