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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is largely covered. The description adds the human-confirmation requirement and account scoping, but omits behavior on batch partial failures, whether deletion is reversible, and the 100-item cap.

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, front-loaded with the action and scope, followed by the confirmation caveat. No filler, though the extreme brevity leaves gaps that additional structure could have filled.

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 destructive, idempotent, non-open-world mutation with no output schema, the description covers the essentials an agent must know (what is deleted, from where, confirm first). It omits partial-failure semantics, reversibility, and the batch size constraint, which matter for a delete-by-list operation.

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 only 50%: request_id is documented in the schema, but lead_ids carries no description, and the description does not compensate by mentioning it is a batch of 1-100 UUIDs. Nothing is said about how request_id enables safe retries for this destructive operation.

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 (delete) and resource (saved leads) plus scope (the selected account), which distinguishes it from siblings like delete_list, delete_status, and update_saved_lead. It stops short of explicitly naming a sibling it is often confused with, so it lands just below a 5.

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?

'Ask the user before deleting' is a real usage directive that tells the agent to confirm prior to invocation, which is valuable. However, there is no guidance on when to use this versus update_saved_lead (soft alternative) or when-not to use it, so the guidance is implied rather than complete.

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