books_delete_customer

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

The schema already provides destructiveHint: true, but the description adds no additional behavioral context beyond the verb 'Delete'. It does not disclose irreversibility, cascading deletions, permission requirements, or any side effects. The description simply restates what the hint already implies, offering no new value.

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, clear sentence with no unnecessary words. It is appropriately sized for a straightforward delete operation and front-loads the essential action, making it easy to parse.

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 destructive operation, important context is missing: whether the deletion is permanent, whether it requires special permissions, or whether it is blocked if related records exist. The description, combined with a sparse schema (one param, no output schema), leaves significant gaps for an agent to fully understand the operation's implications.

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 0% for the customer_id parameter, and the description does not explain its format, purpose, or how to obtain it. Although the parameter name is self-explanatory, the description fails to compensate for the missing schema description, which is required at this low coverage level.

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 uses the explicit verb 'Delete' with the resource 'customer' and system 'Books', making the action and target unmistakable. It clearly distinguishes from sibling tools like books_delete_item or books_delete_invoice, and complements the customer lifecycle tools (create/get/update).

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as whether the customer must have no existing invoices or orders, nor does it suggest checking the get/update siblings first. The single sentence only states the action with no context.

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