Create broadcast campaign

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the campaign starts as a draft, or queued if schedule_at is set, and that it does not send until send_campaign is called. This adds meaningful behavioral context beyond a simple 'create' statement.

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 two concise sentences, front-loaded with the main purpose and followed by essential workflow details. Every word adds value with no 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 7 parameters and no output schema, the description covers the creation workflow but omits what the tool returns (e.g., campaign ID needed for send_campaign). It does not explain how to reference the created campaign, which is a notable gap for successful invocation.

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. The description adds value by clarifying that 'schedule_at' changes the initial state to queued, and that contacts are inline. These details go beyond the schema's field descriptions.

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 a LoginWA broadcast campaign' with specific verb 'Create' and resource 'broadcast campaign'. It further specifies 'inline contact list' and distinguishes from siblings by noting it only creates, not sends ('Call send_campaign to begin').

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 provides clear context on the tool's role: it creates a draft (or queued) campaign, and instructs to call send_campaign to start sending. This implies an alternative workflow and when to use this tool, though it does not explicitly state 'when not to use'.

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