deleteLead

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

Beyond annotations (destructiveHint=true), description confirms 'Permanently delete', 'cannot be undone', 'No soft-delete', and warns to 'confirm intent before bulk use'. No contradiction with annotations.

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?

Well-structured: summary line, usage guidance, required field, destructive warning, return info. No fluff. Front-loaded with purpose.

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 simple input schema and rich annotations, description covers all needed aspects: purpose, when to use, behavioral warnings, return format. Sufficient for agent to invoke correctly.

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?

Single required parameter lead_id, schema coverage 0%. Description only repeats 'Required: lead_id' without adding meaning (e.g., format, source, or constraints). Fails to compensate for missing schema descriptions.

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?

Clearly states verb and resource: 'Delete a lead - Permanently delete a lead record by ID.' Distinguishes from siblings like deleteClick by specifying 'lead'. Mentions alternative updateLead for preservation.

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 says when to use: 'removing a spam or test lead.' Provides alternative: 'use updateLead with a status change instead.' Also references updateLead in 'See also.'

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