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

Beyond annotations, the description discloses the key side effect that the campaign may start emailing recipients, the two-step preview/confirmation flow, the skip behavior for already-sent creators, and that the call is free. These are material operational traits not captured by the annotations. The description is consistent with readOnlyHint=false and idempotentHint=true.

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 front-loaded with the core action and outcome, then moves into input sourcing and the confirmation flow. It is dense but efficient; the parenthetical app-reference wording is slightly redundant. Every sentence adds useful operational information.

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 mutation tool with no output schema, the description covers the essential workflow, side effects, lead-id sourcing, and confirmation requirement. It does not describe what the preview contains or how to obtain campaign_id, but the annotations and schema carry some of that burden. An agent has enough to invoke it correctly, with minor remaining gaps.

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?

With 63% schema coverage and 8 parameters, the description compensates for the most important gaps: where lead_ids come from, how chat_id/list_id are used, and how confirmation_token must be handled across the two calls. It does not explain where campaign_id comes from or clarify uid/bearer_token auth parameters, leaving some schema details to the schema itself.

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 states a specific verb and resource: adding unlocked creators with emails to an Instantly or Smartlead campaign. It clarifies the concrete outcome (the campaign may start emailing them), which distinguishes it from drafting/outreach tools among the siblings. An agent can tell exactly what this tool does without opening the 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?

It gives explicit conditions and sources: use CRM lead ids from list_crm_leads, or chat lead ids together with chat_id or list_id. It also defines the required two-step confirmation workflow and notes that already-sent creators are skipped. This is enough for an agent to choose the right inputs and sequence without guessing.

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