google_ads_ads_update_status

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

With no annotations provided, the description carries full burden. It discloses that the operation is lightweight, writes only the status field, does not reset learning signals, returns the ad ID and new status, and is reversible. This is comprehensive, though it could mention authentication or prerequisites.

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?

Three sentences, each serving a purpose: action, behavioral notes, return/reversibility, and usage guidance. No filler, front-loaded with key information.

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 the tool's simplicity (4 parameters, no output schema), the description covers the essential aspects: what it does, return value, reversibility, and differentiation. Could optionally mention prerequisite states but is adequate.

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 documentation coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema: it confirms customer_id is optional with fallback and reiterates the status enum. No additional semantic richness.

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?

Description clearly states it sets the delivery status to one of three enum values (ENABLED, PAUSED, REMOVED). It differentiates from the sibling tool google_ads_ads_update by specifying it only changes the status field versus the creative copy, making the purpose distinct.

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 states when to use this tool ('Use this for pause/resume') and when to use the alternative ('use google_ads_ads_update to change the creative copy itself'). Also mentions reversibility via rollback_apply, providing clear context.

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