zuckerbot_pause_campaign

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

With no annotations to provide safety or side-effect context, the description carries the full burden. It discloses that pausing stops delivery and spend immediately, leaves the object in Meta, reports the prior status, and that resume is currently unavailable through ZuckerBot. This is notably transparent for a state-changing tool.

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?

Four punchy, front-loaded sentences cover purpose, impact, level selection, and resume caveat without filler. Every sentence earns its place and the most important operational consequence—stops delivery and spend—appears early.

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?

This is a state-changing tool, but the description covers what stops, what persists in Meta, the response behavior (prior status), and the unsupported resume flow. There is no output schema, and the description does enough for an agent to call this confidently and understand the likely result.

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 100%, and the schema already documents entity_level, entity_id, campaign_id, and action. The description's 'set entity_level and pass the matching id' summarizes the relationship but does not add substantial parameter meaning beyond what the schema provides, so it sits at a baseline 3.

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 states a specific verb and resource: pause/delivery across campaign, ad set, and ad levels, with 'campaign' as the default. This clearly differentiates it from sibling tools like activate_campaign, delete_audience, or get_campaign.

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?

It explains when to use adset/ad level vs. campaign level by explicitly saying to 'stop an underperformer WITHOUT killing the winners in the same campaign.' It also tells the agent that resume is not available through ZuckerBot and must be done in Meta Ads Manager, which is grounded, actionable guidance.

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