meta_ads_campaigns_enable

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

With no annotations, the description must carry the burden. It accurately describes the action (setting status to ACTIVE), the scope (campaign only, not sub-entities), the return value (campaign id and new status), and reversibility. It lacks information on permissions or side effects but is still strong.

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 concise: three sentences, each delivering distinct value. The first states the core action, the second explains sub-entity behavior and alternatives, the third covers output and reversibility. No fluff.

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 simplicity of the tool (enable a campaign), the description covers all necessary context: purpose, usage guidance, behavioral details, and output. Even without an output schema, it mentions the return values. It is complete.

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%, so baseline is 3. The description does not add much beyond the schema: it notes account_id is optional and falls back to configured credentials, but the schema already states that. The description for campaign_id is clear but not enriched.

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's purpose: 'Resumes a paused campaign by setting its status to ACTIVE.' It distinguishes from siblings like meta_ads_ad_sets_enable and meta_ads_ads_enable by noting that sub-entities do not auto-resume.

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?

When to use is explicit: to enable a campaign. The description also tells when not to rely solely on this tool (if ad sets/ads are paused, enable them separately) and notes reversibility via rollback_apply or meta_ads_campaigns_pause.

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