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

Annotations declare openWorldHint=false and destructiveHint=false, so the safety profile is partially covered. The description adds meaningful behavioral context: validation occurs before launching and emails start sending per the campaign schedule. However, it does not disclose what happens on validation failure, required permissions, or side effects like sending emails to leads.

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, front-loaded with the action, no filler. Efficient and clear, though it could be tightened by combining the validation and sending behavior into fewer words.

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 single-parameter mutation tool with no output schema and basic annotations, the description covers the core action and validation behavior. It does not explain return values (none expected), but that is acceptable. Some gaps remain around failure handling and idempotency.

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%, and the description provides no parameter syntax or format beyond the schema. The description does mention the campaign configuration, but there is no additional parameter detail. Baseline 3 is appropriate when the schema already documents the single 'id' parameter.

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 and resource ('Launches a new campaign or resumes a paused one') with a clear dual behavior. It is distinguishable from pause_campaign, resume_autopilot_run, and copilot_launch, but does not explicitly name or differentiate against neighboring sibling tools like pause_campaign or copilot_launch.

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 when to use it (to launch or resume), but does not state preconditions or alternatives. It does not explain when to use launch_campaign vs resume behavior vs paused-campaign handling, or how it relates to pause_campaign.

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