delete_customer

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

The description indicates the destructive nature of the tool and the safety requirement. However, without annotations, it lacks details on side effects (e.g., cascading deletes), irreversibility, or permissions, leaving room for improvement.

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 that gets straight to the point. No unnecessary words or information.

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 description is minimally sufficient given the presence of an output schema. However, it does not mention what the tool returns (e.g., success status or deleted object), which could be helpful for an agent.

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%, so the baseline is 3. The description reiterates the 'confirm' requirement but adds no new meaning beyond the schema's parameter descriptions and titles.

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 action ('Delete') and the resource ('customer'), making the tool's purpose immediately obvious. Among sibling tools, it uniquely targets customers, distinguishing it clearly from other delete tools.

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 explicitly requires 'confirm=true', providing a key usage condition. While it doesn't specify when not to use this tool or mention alternatives, the context is clear for its intended use case.

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