Delete Lead

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

The description adds significant context beyond annotations: it emphasizes permanence ('Cannot be undone'), mentions 'personal data' deletion, and links to legal frameworks. This goes beyond the destructiveHint=true annotation by explaining the real-world impact and data privacy implications.

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?

Two concise sentences deliver all essential information: what, how, when, and consequences. Zero waste, and the key message is 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?

For a simple delete tool with only 2 optional parameters and no output schema, the description covers the purpose, usage context, and irreversibility. It doesn't describe return values, but that's expected for a delete operation. Could mention response behavior but not essential.

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 schema already provides 100% coverage with both parameters described as 'Provide either email or id.' The description reinforces this but doesn't add new semantic details such as format or validation. Baseline 3 is appropriate since the schema carries the parameter documentation.

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 specific verb 'permanently erase' with clear resource ('a lead'), and distinguishes it from sibling delete tools (hyros_delete_call, hyros_delete_sale) by specifying the target (lead) and the method of identification (email or id).

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 explicitly states when to use (GDPR/CCPA right-to-erasure requests) and provides clear context that this is for permanent deletion. While it doesn't name alternatives or exclusions, the purpose is obvious and privacy-related. It could be improved by mentioning that other delete tools exist for other resource types, but the context is sufficient.

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