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

Annotations already declare destructiveHint/readOnlyHint, but the description adds substantial context beyond them: exactly what is destroyed, that mid-campaign contacts are refused unless forced, that CRM leads survive unlinked by default, and that the action cannot be undone and requires explicit user consent.

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 dense sentences, each carrying distinct information, with the permanence warning and cascade effects front-loaded ahead of the escape hatches and confirmation procedure. No filler.

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 multi-param tool with no output schema, the description covers purpose, cascades, refusal/override rules, alternatives, and the consent workflow. Nothing an agent needs to call it safely is missing.

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%, so baseline is 3, but the description adds meaning the schema lacks: the refusal/override relationship for force, the default-preserving behavior of delete_crm_leads, and a concrete confirm workflow (show contacts first, then confirm) rather than a bare boolean.

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 (permanently delete) and resource (saved contacts/LinkedIn profiles) plus the full scope of the cascade: campaign memberships, scheduled actions, and campaign history. An agent can distinguish this from siblings like remove_contacts_from_list or delete_crm_leads without opening a 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?

Explicitly names the alternative (exclude_contacts_from_campaign) and the condition that selects it (goal is just to stop outreach). Also gives the guardrail for force: true and the precondition for confirming an irreversible deletion.

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