delete_lead

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

No annotations are provided, so the description bears full responsibility. It only states the action ('Delete'), which implies destructiveness, but does not disclose consequences (e.g., permanent removal, cascading effects), authorization needs, or error states. This is minimally transparent.

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?

The description is a single, short sentence that gets to the point. It is front-loaded and efficient, though it could benefit from slightly more structuring (e.g., mentioning expected response or usage note).

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 the simplicity of the tool (1 param, no nested objects, no output schema), the description is minimally complete but lacks any mention of return values, error conditions, or side effects. For a delete operation, it should at least hint at the response (e.g., 'returns success or error').

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 has 100% coverage: the only parameter 'leadId' is described as 'Lead ID to delete'. The description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 a specific verb ('Delete') and resource ('lead'), and specifies the method ('by its ID'). It clearly states what the tool does, though it lacks differentiation from sibling tools like 'delete_post' which follow the same pattern.

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?

No guidance is provided on when to use this tool vs alternatives (e.g., 'update_lead_status' or 'get_single_lead'). The description does not mention prerequisites, contexts, or situations where deletion is appropriate or not.

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