Launch a campaign

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden. It usefully discloses two behavioral facts: the campaign is created in a paused state and requires preview confirmation. It does not say whether an ad account must already be connected (a sibling, connect_ad_account, suggests that prerequisite) or what happens on failure.

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 short sentences with no filler; the core action is front-loaded and the paused/preview caveat follows immediately. Every clause 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?

For a zero-parameter mutation tool with no output schema, the description covers the basic lifecycle state (starts paused) but omits account prerequisites and output expectations. It is minimally adequate rather than complete.

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?

The tool takes zero declared parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The empty schema has additionalProperties=true, which the description does not address, but with no named parameters there is no semantics gap to compensate for.

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?

Names a specific verb ('Create') and resource ('a new campaign') plus the target scope ('your connected ad account'), so the action is unambiguous. However, it does nothing to separate itself from the many channel-specific siblings (launch_meta_ad, launch_search_campaign, launch_pmax_campaign, launch_tiktok_campaign), leaving the agent to guess when the generic tool applies.

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 clause 'after you confirm a preview' implies a prerequisite workflow step, which is more than most definitions offer. But there is no explicit when-to-use versus the other launch_* tools, and no stated exclusions or conditions for picking the generic launcher over a channel-specific one.

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