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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds business-rule context the annotations cannot express – the invoice/recurring-invoice blocking condition – though it does not say whether the delete is a permanent hard delete or what error surface a blocked attempt produces.

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?

Three short sentences with zero padding: purpose first, required input second, blocking condition third. Every sentence carries distinct 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?

For a single-parameter destructive tool with full schema coverage and explicit annotations, the definition covers purpose, required input, and the main failure condition. The only real gap is the permanence/cascade behavior of the deletion, which would help an agent decide before invoking a destructive call.

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% and the single parameter 'id' is already documented as 'Customer ID to delete'. The sentence 'Requires the customer ID' only restates what the schema makes mandatory, adding no format, source, or lookup detail.

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 opens with a specific verb+resource ('Delete a customer record'), which is unambiguous and self-differentiating from the many delete_* siblings for other resources. It does not explicitly name or contrast a sibling, but the resource noun does the disambiguation work.

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?

It supplies a concrete precondition/exclusion: customers with existing invoices or recurring invoices cannot be deleted, which tells the agent when a call will fail. It stops short of a full 5 because it names no alternative (e.g., update or deactivate) for customers that cannot be deleted.

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