google_ads_ads_update_status

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

Discloses that tool is lightweight, writes only status, does not reset learning signals, returns ad ID and new status, and that REMOVED is a soft delete (ad stops serving but remains queryable). No annotations present, so description fully carries burden.

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?

Four sentences, front-loaded with core action. Every sentence adds necessary information without redundancy.

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?

For a simple status update tool with 4 params and no output schema, description provides adequate context: lightweight nature, no learning signal reset, return info, and reversibility.

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 parameters fully (100% coverage). Description adds value by explaining REMOVED as soft delete and customer_id fallback behavior. While schema descriptions suffice, extra context warrants a 4.

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 it sets delivery status to ENABLED, PAUSED, or REMOVED. Specifies it's lightweight and only writes the status field. Explicitly differentiates from sibling google_ads_ads_update, which changes creative copy.

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?

Provides explicit guidance: 'Use this for pause/resume; use google_ads_ads_update to change the creative copy itself.' Also notes 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.