ads_create_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 campaigns default to PAUSED for safety, that confirm must be true to actually create, and explains budget units with an example. It does not disclose rate limits or error behavior, but for a create tool, the key safety and confirmation behaviors are well covered.

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 efficiently structured as a purpose statement followed by a compact Args list. Every line adds unique value—no fluff or repetition. The front-loaded purpose and the clear parameter breakdown make it easy to scan.

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 (10 parameters, no annotations, no output schema), the description is remarkably complete. It explains all parameters, default behaviors, safety mechanisms, and budget semantics. The only minor gap is lack of return-value description, but that is not required when no output schema exists and the rest is so thorough.

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 schema has 0% description coverage, so the description fully compensates by explaining every parameter: objective enum values, special_ad_categories options, budget meaning with an example, bid_strategy choices, buying_type default, and the confirm flag's role. This goes far beyond the schema's bare properties.

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 new campaign' with a specific verb and resource. It distinguishes itself from sibling tools like ads_update_campaign and ads_pause_campaign by focusing on creation, and adds the safety default of PAUSED, reinforcing its purpose.

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 for when to use: it is for creating new campaigns, not updating or pausing. It also includes critical usage guidance like 'confirm: Required True to actually create' and the default PAUSED status. However, it does not explicitly name alternatives or state when not to use it, so it misses a full 5.

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