create_campaign

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

No annotations are provided, so the description carries full burden. It reveals default status, required fields, and budget level options, but omits important behavioral traits such as authentication requirements, ad account context, side effects, or response structure. This is insufficient for a mutation tool.

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?

Three sentences with no filler. Front-loaded with the main action, each sentence adds distinct value. Extremely concise and well-structured for quick understanding.

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 of campaign creation and the presence of many sibling tools, the description covers the core purpose and key parameters. However, it lacks output schema information and does not mention account context or post-creation steps, leaving some gaps for an agent to fully understand the tool's usage in workflow.

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%, baseline 3. The description adds value by clarifying that budget can be set at campaign or ad set level, which explains the relationship between daily_budget and lifetime_budget. It also reinforces defaults and requirements, exceeding the schema's 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 the tool creates a new ad campaign, specifying verb (create) and resource (campaign). It adds key details like default status, required fields, and budget flexibility, distinguishing it from sibling tools like create_ad or copy_campaign.

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 usage for creating campaigns but does not explicitly state when to use this tool versus alternatives like copy_campaign or update_campaign. It mentions budget level flexibility but lacks guidance on context or exclusions.

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