Smartlead: remove an entry from the block list

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

The description goes well beyond the annotations by detailing the runtime effects: it deletes a suppression record, re-enables sending to a previously blocked recipient, and classifies itself as DESTRUCTIVE. It also includes an endpoint URL and a safety summary. This exceeds what the annotations alone provide, offering clear expectations about the tool's side effects and prerequisites.

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 structured in short lines, each delivering a distinct piece of information (action, safety, endpoint, guardrails, prerequisite). It is longer than necessary but remains focused and easy to scan. The front-loaded sentence states the core purpose and consequence clearly.

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?

With an output schema present, the description does not need to explain return values. It covers the purpose, prerequisites, safety classification, and related sibling tool for verification. The combination of schema, annotations, and context signals is comprehensive enough for an AI agent to use this tool correctly and safely.

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 already covers both parameters with descriptions, and the description reinforces the semantics by stating that the id comes from smartlead_get_domain_block_list and that confirm_destructive must be true. This adds useful context beyond the schema, though it does not introduce new parameters or change the baseline understanding.

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 clearly identifies the resource ('one entry from the global block list') and its consequence ('re-enabling outreach to that domain or address'). It also distinguishes itself from sibling tools like smartlead_get_domain_block_list and smartlead_add_domain_to_block_list by specifying the exact destructive action.

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 explicitly states a prerequisite action ('Call smartlead_get_domain_block_list first to confirm which entry the ID refers to') and required configuration (unrestricted mode, SMARTLEAD_MCP_ALLOW_DESTRUCTIVE=true, confirm_destructive: true). It leaves no ambiguity about when and how to invoke this tool, including the need for explicit confirmation.

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