Delete Lead from Workspace

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

Annotations already flag destructiveHint=true, and the description reinforces this with 'permanently al delete,' adding irreversibility beyond the annotation. It does not disclose side effects like removal from lists/campaigns or inability to undo, but the destructive annotation covers the core safety profile.

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, no filler, front-loaded action verb, and every word contributes. The description is appropriately sized for the tool's simplicity.

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?

The tool is simple, with a complete input schema and an output schema, so the short description may be sufficient. However, given its destructive nature, it would benefit from clarifying that deletion is workspace-level and distinct from removing a lead from a campaign, making it slightly under-specified.

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 description coverage is 100%, with linkedin_url fully described as 'Lead's full LinkedIn profile URL.' The tool description adds no additional parameter semantics, so the baseline 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 the exact action ('permanently delete') and resource ('a lead from the workspace'), clearly distinguishing it from the sibling remove_lead_from_campaign, which only removes a lead from a campaign. The verb and target are unambiguous.

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 word 'permanently' implies this is for full deletion rather than campaign removal, but the description does not explicitly contrast it with remove_lead_from_campaign or state when not to use it. Usage context is implied, not stated.

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