Create Campaign

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

The description discloses behavioral traits beyond annotations, such as return value (new campaign ID), parameter constraints (lifetime budget requires stop_time), and the migration alternative. Annotations indicate non-destructive write, which aligns with creation. No contradictions.

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 relatively concise and well-structured, starting with purpose and listing arguments. Each sentence adds value, though the list format could be slightly more compact.

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 (9 parameters, 3 required, no output schema), the description covers purpose, parameters, usage, and return value adequately. It lacks error handling or rate limit details but is sufficient for a creation tool.

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 description adds meaning beyond the input schema by explaining common values for objective and clarifying the relationship between lifetime_budget and stop_time. Schema coverage is high (89%), but the description still provides useful context.

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 creates a new campaign in a Meta ad account, using specific verbs and resources. It differentiates from sibling tool meta_migrate_campaign_to_advantage_plus by noting the migration path for Advantage+ Shopping campaigns.

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 explicit guidance on when to use this tool for standard campaigns and when to use alternative tools (e.g., for Advantage+ campaigns). It also notes special requirements for special_ad_categories in certain verticals.

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