meta_ads_campaigns_pause

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

Discloses cascading behavior ('nothing underneath will serve'), lightweight nature, reversibility, and return info. Without annotations, this is good but could mention prerequisites like campaign being active.

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?

Two dense sentences with zero waste. Front-loaded with verb and resource, then cascading effect, reversibility, return, and usage guidance.

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 simple pause action, description covers purpose, usage, behavior, and return. Lacks some edge cases (e.g., already paused) but sufficient for typical use.

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% with both params described. Description doesn't add beyond schema, baseline 3 as per rules.

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?

Clearly states it pauses a single campaign by setting status to PAUSED, with cascading effect on ad sets and ads. Distinguished from soft-delete via update with DELETED status.

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?

Explicitly says 'Use for immediate stop-spend situations' and contrasts with soft-delete via update. Mentions reversibility via rollback or enable, providing clear when-to-use guidance.

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