meta_ads_ads_pause

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

With no annotations, the description carries full burden and does so well: it discloses 'Lightweight; the ad stops serving immediately', reversibility, return value ('Returns the ad_id and new status'), and scope ('Does not affect the parent ad set or sibling ads'). No contradictions.

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 short sentences, front-loaded with the core action, then reversibility, return value, and scope. Every sentence adds unique value with 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?

For a simple single-ad pause operation, the description is complete: it covers the action, immediate impact, reversal, return data, scope boundary, and usage guidance versus alternative. The schema covers parameters fully, and the description even mentions output without needing an output schema.

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 adds no extra parameter semantics beyond what the schema already provides; it does not elaborate on account_id or ad_id, but the schema descriptions are sufficient.

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?

Description uses a specific verb+resource: 'Pauses a single ad by setting its status to PAUSED.' It clearly distinguishes from sibling tools by specifying scope: 'Does not affect the parent ad set or sibling ads' and differentiates from meta_ads_ad_sets_pause.

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 when to use this tool vs alternatives: 'Use for creative-level pause; use meta_ads_ad_sets_pause to stop a whole ad set.' Also mentions reversal paths via rollback_apply or meta_ads_ads_enable, giving clear context for when this tool fits.

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