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 largely carried by structured data. The description adds that the effect is permanent and irreversible, which is meaningful reinforcement, but it does not say whether related records (conversations, campaign membership, meeting flags) are also removed, what happens if the ID does not exist, or what the response contains.

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 short sentences, zero filler, with the permanence warning placed immediately after the action statement so the most consequential fact 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 single-parameter delete tool with full schema coverage and annotations covering destructiveness and idempotency, the description is close to sufficient. The remaining gap is the fate of dependent data and error behavior for a nonexistent ID, which matters for a mutation tool but is a modest omission.

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 schema already explains the numeric lead ID is the value returned at creation time. The description only repeats "by ID" and adds no format, origin, or edge-case detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("Permanently deletes a lead by ID"), which is enough to separate it from delete_campaign or delete_icp without reading further. It stops short of explicitly naming a sibling it could be confused with, so it is clear but not maximally differentiated.

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?

There is no guidance on when to delete a lead versus alternatives such as update_lead, move_lead_to_campaign, or adding to the blocklist, and no prerequisite or confirmation guidance for a destructive action. The agent must infer the situation entirely from the name.

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