gdpr_delete_customer_data

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

Discloses that CRM records are anonymized rather than deleted, which is critical behavioral information. No annotations exist, so description carries full burden; it does so well.

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?

Single sentence with all key info: purpose, side effect, and required confirmation. No wasted words, front-loaded.

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?

Given no output schema and two parameters, description explains the core action and side effect. Sibling tool for export provides differentiation. Missing output format or return value, but adequate for a delete operation.

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 covers both parameters with descriptions; description adds no extra semantic value beyond echoing that confirm is for dangerous action. Baseline score of 3 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?

Clear verb ('Eliminar'), specific resource ('datos del cliente'), GDPR context, and distinguishing sibling tool (gdpr_export_customer_data). No ambiguity.

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?

Explicitly states requirement for confirmation parameter. Implies this is a dangerous delete operation, but doesn't explicitly state when not to use or alternatives beyond the sibling export tool.

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