meta_ads_campaigns_pause

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

Discloses cascade effect on child entities, reversibility, and return value. No contradictions with missing annotations, but could mention any necessary permissions or rate limits.

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?

Three sentences front-loaded with action, efficient and no redundancy.

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?

Covers purpose, effect, return, and alternatives. No output schema needed because return is described. Complete for a simple pause 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?

Schema already provides full coverage with good descriptions. Description adds little beyond mentioning the return value, which is not parameter-specific.

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?

Clear verb (pauses) and resource (campaign) with specific action (setting status to PAUSED). Distinguished from soft-delete via update, and mentions cascade to ad sets/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?

Explicitly states use case (immediate stop-spend) and alternatives: reverting via rollback_apply or enable, or soft-delete via update with status='DELETED'.

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