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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's 'Reversible' is genuinely additive: it clarifies that pausing is a state change that can be undone, not a deletion. However, it doesn't say whether pausing a campaign cascades to its ad sets/ads, what permissions or account context are required, or what happens to already-paused entities.

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 short sentences, zero filler, with the core action front-loaded ahead of the reversibility note. Nothing is wasted or buried.

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 mutation tool with no output schema, 0% schema coverage, and an unexplained second parameter, the definition is thin. It omits cascade behavior for nested entities, error/partial-failure semantics for a batch of IDs, and the role of meta_account_id — all things an agent needs before calling it safely.

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 description coverage is 0%, so the description must carry the burden and largely fails: 'by ID' hints that campaign_ids takes identifiers but not the format, array limits, or behavior for invalid IDs. The second parameter, meta_account_id, is never mentioned at all, leaving the agent to guess whether it is required in multi-account contexts.

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?

States a specific verb (Pause) and resource scope (campaigns/ad sets/ads) plus the lookup key (by ID), so the agent knows exactly what operation it performs. It doesn't name the closest siblings (resume_campaigns, delete_campaigns) explicitly, and there is mild tension between the tool name 'pause_campaigns' and the broader 'ad sets/ads' claim given the parameter is campaign_ids.

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?

'Reversible' implies this is the softer alternative to delete_campaigns, and the sibling set makes resume_campaigns the obvious counterpart, but the description never states when to choose pause over delete or resume. Usage is inferable rather than stated.

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