google_ads_ads_update

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

With no annotations, the description carries full burden. It discloses major behaviors: wholesale replacement, no per-asset patch, omitted side preserved, ad replaced under same ID, learning reset, re-review, non-reversibility, and rollback suggestion. Exceptionally transparent.

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?

Description is somewhat long but every sentence adds essential information: purpose, replacement semantics, preservation behavior, return value, side effects, rollback advice, and alternative tool. No redundancy or filler.

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 mutation tool with no annotations and no output schema, the description is exceptionally complete. It covers what the tool does, how it behaves, side effects, reversibility, and when to use alternatives. The only missing pieces are already covered by schema descriptions.

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%, so baseline is 3. The description adds key semantic value by explaining that supplied side is fully replaced and omitted side preserved, which is critical for correct use of headlines/descriptions parameters. It also clarifies fallback behavior for customer_id via schema, but description reinforces it.

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 clearly states it updates creative copy of an RSA by replacing headlines/descriptions. It explicitly distinguishes from google_ads_ads_update_status for status-only changes, avoiding confusion with sibling tools.

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 when-to-use guidance: creative copy updates, with full side replacement semantics. Names the alternative google_ads_ads_update_status for pause/resume and recommends mureo_state_action_log_append for rollback, covering both usage and exclusions.

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