pause_ad

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

No annotations are provided, so the description carries the full behavioral burden. It mentions that the ad should be active, but does not disclose side effects such as stopping delivery, changing status, idempotency, or whether pausing is reversible.

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 a single, front-loaded sentence with no filler or redundant wording. It could be slightly expanded with usage guidance without becoming bloated, but as written it is clear and efficiently structured.

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 mutating tool with no annotations and no output schema, the description is too thin. It omits lifecycle context, alternate actions, account scoping, and expected outcome, leaving an agent with insufficient information to invoke it confidently.

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 only 50%: ad_id is minimally described, while ad_account_id has no description at all. The tool description adds no parameter-level meaning, so an agent cannot determine the role, optionality, or constraints of ad_account_id from the definition.

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 uses a specific verb ('pause') and resource ('ad'), and the qualifier 'active' clarifies the intended target state. This clearly distinguishes it from sibling tools like pause_ad_account, pause_campaign, or archive_ad.

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?

The description provides no guidance on when to use this tool versus alternatives such as activate_ad, archive_ad, pause_campaign, or pause_ad_account. It states what the tool does, but not when it should be chosen over related lifecycle tools.

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