google_ads_keywords_remove

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

No annotations provided, so description carries full burden. Discloses soft-delete, return of criterion_id, destructiveness, reversibility with rollback_apply, and the important caveat that rollback loses quality score and learning. This is thorough behavioral context.

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, front-loaded with core action, concise and no extraneous information. Every sentence adds value.

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 removal tool with no output schema, the description explains the return value (criterion_id), the nature of the operation (soft-delete), and rollback implications. No gaps in what an agent needs to correctly invoke and understand the tool.

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?

Input schema covers all 3 parameters fully (100% coverage). Description does not add extra meaning beyond the schema. Baseline of 3 applies as the schema already provides sufficient parameter descriptions.

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 removes (soft-deletes) a single keyword criterion from an ad group. Distinguishes from sibling google_ads_keywords_pause by noting that pause is preferred for temporary suspension, making the purpose specific and differentiated.

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 provides when to use this tool and when not: 'For temporary suspension prefer google_ads_keywords_pause, which preserves all signals.' Also mentions rollback behavior, guiding when to use rollback instead.

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