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

No annotations provided, so description must convey behavior. It discloses that the tool creates and immediately schedules, and mentions the optional scheduleAt parameter for future sending. However, it does not describe potential side effects, error behaviors, or whether it is destructive (e.g., replacing existing campaigns).

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?

Two sentences with no filler. The first sentence immediately states the core purpose; the second provides critical parameter selection guidance. Every word earns its place.

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 complexity (13 parameters) and no output schema, the description is moderately complete. It covers main parameter choices but omits return value behavior (e.g., whether it returns campaign ID or status). An agent might need to infer output from context.

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 69%, and the description adds value by clarifying mutual exclusivity groups (audienceId/segmentId/topicId/filter, html/templateSlug) that are not explicit in the schema. This helps agents understand constraints beyond individual parameter 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 it is a one-shot broadcast that creates and immediately schedules a campaign. It specifies the key resource ('campaign') and action ('create and schedule'), and distinguishes from siblings like create_campaign and schedule_campaign by emphasizing the atomic nature.

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 gives explicit guidance on parameter selection: 'Pass either an audienceId, segmentId, topicId, or fully-qualified filter' and 'Provide html OR templateSlug'. However, it does not explicitly mention when to use this tool versus creating and scheduling separately, though it is implied.

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