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 the full burden of disclosing side effects and behavior. It says 'Lightweight — writes only the status field and does not reset learning signals,' 'Returns the ad ID and new status,' and 'Reversible via rollback_apply.' These details go beyond the schema and give critical context about the tool's impact and reversibility.

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?

The description is three concise sentences, front-loaded with the core purpose and followed by key behavioral notes and usage guidance. Every sentence serves a purpose with no redundancy or filler. Ideal length for this tool.

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?

The tool is a simple status update with four well-documented parameters and no output schema. The description covers purpose, side effects, return value, and alternative tool usage, making it complete for an agent to select and invoke correctly. No gaps are apparent.

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%, so parameters are fully described in the input schema. The description adds no extra parameter information beyond what the schema provides (e.g., it doesn't elaborate on customer_id or ad_group_id). Baseline of 3 is appropriate since the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Sets the delivery status of a single ad to ENABLED, PAUSED, or REMOVED.' This clearly states the tool's function and enumerates valid values, making it distinct from siblings like google_ads_ads_update, which is explicitly differentiated later.

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?

The description provides direct usage guidance: 'Use this for pause/resume; use google_ads_ads_update to change the creative copy itself.' This explicitly tells when to choose this tool over an alternative, satisfying the dimension fully.

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