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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description is not burdened with the basic safety profile. It goes further, disclosing the concrete consequence (previously blocked prospects become targetable again) and why that is dangerous (opt-outs, competitors, do-not-contact requests leaking back into campaigns). That is exactly the value-add this dimension rewards.

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?

Three sentences, front-loaded with the action, then the risk, then the scoping caveat. The risk statement sits ahead of the workflow instruction, which is the right priority for a destructive tool, and nothing is padded.

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?

A one-parameter destructive tool with full annotation coverage and no output schema needs exactly this: consequence of the mutation, pre-call verification workflow, and disambiguation from the similarly named blacklist tools. All present; no return-value explanation is required.

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 coverage is 100% and the single parameter is already documented as a blacklist rule id sourced from `blacklist_list`. The description repeats that provenance rather than adding new meaning about the id's format or behavior. Baseline 3 is correct when the schema does the work.

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+resource ('Remove an exclusion rule') and immediately distinguishes the scope from the nearest confusion point: it removes a rule, not a blacklisted person, which is handled by `lead_blacklist`. An agent can separate this from `blacklist_list`, `blacklist_add`, and `lead_blacklist` without opening any schema.

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?

Gives an explicit pre-call procedure: read the rule with `blacklist_list`, show the user exactly what it blocks, and obtain an explicit yes. It also names the alternative record path (`lead_blacklist`) and notes no tool removes that record, so both the when and the when-not are covered.

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