delete_leadDelete a lead permanently by its record ID. This action cannot be undone and requires leads:write scope.
Permanently delete a lead. Not reversible.
Requires scope leads:write.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The record id, e.g. "6a96a3ead6e886d42462dd3e". |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds the crucial context that deletion is permanent and irreversible, plus the `leads:write` scope requirement. This goes beyond the annotations without contradicting them.
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 brief sentences convey action, consequence, and authorization with zero waste. The most important information 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 one-parameter destructive operation, the combination of annotations (destructive, idempotent, non-read-only) and description (permanent, irreversible, scope) fully equips an agent to invoke it correctly. No output schema is necessary for a simple delete.
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 description gives no parameter-specific details, but the input schema fully documents the single `id` parameter with an example. With 100% schema coverage, the schema carries the semantic load.
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 specifies the exact action ('Permanently delete') and resource ('a lead'), making the tool's function unmistakable. It also distinguishes it from other lead tools like update_lead or get_lead and from delete_* siblings by naming the resource.
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 implies use when a lead should be permanently removed, but does not explicitly compare this to alternatives or state when not to use it. The required scope is a prerequisite, not a usage guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.