meta_ads_campaigns_create

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

With no annotations, the description carries full disclosure: it explicitly says 'Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back.' It also warns about immediate spend and reinforces the PAUSED default, adding meaningful behavioral context beyond the schema.

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 four sentences with no filler: it front-loads purpose and return value, then covers mutation risk, spend guardrail, and resource hierarchy. Every sentence earns its place and avoids duplicating the full schema.

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 high-stakes create operation with no output schema and no annotations, the description provides the essential operational context: return value, rollback guidance, default status, spend safety, and the required sibling calls to fully create a campaign. It is complete enough for the agent to invoke and chain the tool correctly.

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 already documents all 8 parameters with high detail, so the baseline is 3. The description adds the crucial context that a campaign is only a container and ad sets/ads are separate, which explains why those parameters do not exist here and how the returned id should be used in subsequent calls. It mostly reinforces schema details, so it does not reach 5.

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 states 'Creates a new campaign in the specified Meta Ads account' and notes the return of the campaign id, providing a specific verb, resource, and scope. It also distinguishes itself from sibling tools by explicitly pointing to meta_ads_ad_sets_create and meta_ads_ads_create as the separate steps for ad sets and ads.

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?

It gives clear invocation context: default status is PAUSED and ACTIVE should only be passed after operator confirmation of spend. It names the sibling tools that must be used for ad sets and ads, which clarifies boundaries, though it does not explicitly state 'use this when creating a new campaign' as opposed to updating.

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