launch_campaign

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

Annotations declare destructiveHint=true, and the description confirms this by stating 'Create and activate.' It adds behavioral details: steps are scheduled upfront, suppressed leads are skipped, returns campaignId, and supports idempotency for retry. No contradiction with annotations.

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 a single paragraph of four sentences, front-loaded with the main purpose. Every sentence adds value, and there is no redundancy or fluff.

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?

Given the tool's complexity (8 parameters, nested objects) and lack of output schema, the description covers essential purpose, parameters, and key behaviors (suppressed leads, idempotency). It mentions the return value. Missing some details like default for timezone or sendWindow but sufficient for selection.

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 low (13%), but the description enumerates all key parameters (name, offer, leads, sequence, sendWindow, timezone, stopOnReply, idempotencyKey) and explains the structure of sequence and sendWindow. It adds meaning beyond the schema, especially for idempotency and lead object.

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 clearly states 'Create and activate a campaign on a lead list,' specifying the verb and resource. It distinguishes from sibling tools like list_campaigns (listing) and campaign_results (results) by focusing on the creation and activation process.

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 implies usage for launching campaigns but does not explicitly state when to use this tool vs alternatives or provide when-not-to-use guidance. The context of sibling tools is not leveraged for contrast.

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