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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds real behavioral context the annotations do not: the effect is suppression of future sends from that specific campaign, not a global block. It stops short of stating whether the removal is reversible or what happens if the address is not a lead in the campaign.

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 core effect is front-loaded in the first clause, followed by the scoping rule and then the alternatives. Every sentence carries routing or behavioral information; the trailing docs URL is short and does not bury the payload.

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, return values need no explanation, and both required parameters are fully documented. The only meaningful gap is reversibility and error behavior for a non-member email, which an agent might want before calling a destructive tool, though the existence of argorant_restore_campaign_leads partially signals recoverability.

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 100% and both parameters are documented in the schema, including the hint that campaign_id comes from argorant_list_campaigns. The description only reinforces that 'email' refers to one person in that campaign, adding little syntax or constraint detail beyond the schema, so baseline 3 applies.

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 and resource ('Take one email address out of a campaign') plus the outcome ('nothing more is sent to that person from it'). It explicitly separates itself from argorant_remove_campaign_leads (bulk) and argorant_block (global), so an agent can route correctly 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 use case ('Use it for a single person'), an explicit alternative for the many-person case (argorant_remove_campaign_leads), and an explicit alternative for the broader case (argorant_block). This is the when/when-not/alternatives pattern in three sentences.

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