google_ads_campaigns_update_status

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

With no annotations, description fully discloses lightweight nature (writes only status), return fields (campaign ID and new status), and the soft-delete behavior of REMOVED including reversibility constraints.

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?

Concise, front-loaded with main action, and every sentence adds value. No redundant 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?

Despite no output schema, description covers purpose, parameters, behavior, return values, reversal options, and alternative tools. Complete for a focused status-update tool.

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%; the description adds minimal extra meaning beyond what's in the schema. It does note customer_id fallback and REMOVED soft delete, but these are also in schema descriptions. Baseline 3 is appropriate.

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?

Clearly states the verb 'Sets' and resource 'delivery status of a single campaign' with specific statuses. Distinguishes from sibling google_ads_campaigns_update by specifying it only changes status, not other settings.

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 says 'Use this for pause/resume' and contrasts with sibling tool for other updates. Provides reversal details including rollback_apply and 30-day window for REMOVED.

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