meta_ads_campaigns_create

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

No annotations provided, so the description fully covers behavioral traits. It states 'Mutating — not automatically reversible' and advises rollback recording. It also warns that default status is PAUSED and to only set ACTIVE with operator confirmation, highlighting spend implications. Additionally, it explains that budgets can live on campaign or ad set but not both.

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?

Five sentences, each earning its place. Front-loaded with the primary action and return. No redundant information; tone is direct and informative.

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 (6 params, no output schema), the description covers purpose, return value, mutability, status defaults, budget placement, and dependency on other tools. It is complete enough for an AI agent to understand how to invoke the tool correctly without additional context.

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 description coverage is 100%, so baseline is 3. The description adds strategic context for parameters, such as the default status of PAUSED and the mutual exclusivity of daily_budget and lifetime_budget. It doesn't elaborate on all parameters but provides useful guidance beyond the schema.

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 'Creates a new campaign in the specified Meta Ads account. Returns the new campaign id.' It uses a specific verb (creates) and resource (campaign), and distinguishes from sibling tools like meta_ads_ad_sets_create and meta_ads_ads_create by noting that ad sets and ads are created separately.

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 vs alternatives: 'A campaign acts as a container; ad sets (where budgets and targeting live) and ads must be created separately.' It also advises on setting status to ACTIVE only after operator confirmation, and recommends recording before-state for potential rollback using mureo_state_action_log_append.

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