update_campaign_status

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

With no annotations, the description carries the transparency burden. It clearly discloses the dry-run default and the need to pass confirm=True for execution, which is a key safety behavior. It does not detail side effects, but the 'execute' wording implies the actual status change.

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 sentences, front-loaded with the purpose, and no redundant information. Every word earns its place.

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?

Given a 100% schema coverage and an output schema, the description only needed to add the dry-run safety mechanism, which it does. It could mention permissions or irreversibility, but the dry-run disclosure sufficiently completes the picture for most use cases.

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?

The input schema has 100% documentation coverage for all parameters. The description reiterates the dry-run/confirm behavior that is already in the schema, adding minimal new meaning beyond what the schema provides.

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 clearly states the tool's function: 'Pause or enable a campaign.' This is a specific verb+resource combination that distinguishes it from sibling tools like update_campaign_budget or update_ad_group_status.

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 provides clear context for usage by specifying the action (pause or enable) and the critical dry-run default with confirm=True execution. It does not explicitly contrast with alternatives, but the resource and action make the intended use obvious.

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