google_ads_ads_update_status

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

No annotations provided, so description carries full burden. It discloses lightweight nature, writes only status field, does not reset learning signals, and is reversible. Could add auth prerequisites or rate limits, but covers key behavioral traits.

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: first sentence states core purpose and behavior, second sentence provides usage guidance. No fluff, each sentence 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 4 parameters, no output schema, the description explains return (ad ID and new status), behavior (lightweight, reversible), and relationship to sibling tool. Adequate for agent to use correctly.

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 covers 100% of parameter descriptions. Description adds value by explaining enum values (ENABLED, PAUSED, REMOVED), noting REMOVED is a soft delete, and describing customer_id fallback behavior. Slightly more detail on defaults could push to 5.

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 specifies the action ('Sets the delivery status'), resource ('single ad'), and allowed values (ENABLED, PAUSED, REMOVED). It differentiates from sibling tool google_ads_ads_update by indicating this tool is for pause/resume vs. creative changes.

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 ('Use this for pause/resume') and when to use alternative ('use google_ads_ads_update to change the creative copy'). Also provides context on REMOVED as a soft delete and reversibility via rollback_apply.

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