Permanently remove Google Ads keywords

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'permanently remove' adds modest behavioral context beyond those. It usefully highlights the mandatory confirm_delete safety gate and irreversible framing, but it does not describe downstream effects or what happens to associated data.

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 short sentences front-load the action and then state the required guardrail with no filler. The description is concise and well-ordered, though it leaves some semantic gaps covered by other dimensions.

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?

With destructive annotations and the confirm_delete requirement, the description is minimally adequate for a destructive operation. However, there is no output schema and three parameters lack meaningful descriptions, so an agent must infer what criterion_ids and ad_group_id refer to in Google Ads terms.

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 only 25%, so the description needed to compensate for undocumented parameters. It only mentions confirm_delete, which the schema already constrains to true, and adds no meaning for ad_group_id, criterion_ids, or customer_id.

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 states a specific action ('Permanently remove keywords') and identifies the resource, which clearly signals destructive deletion rather than a status change. It differentiates from add-keyword and set-status siblings, though it does not explicitly name them as alternatives.

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?

No guidance is given for when to use this tool versus alternatives such as google_ads_set_keyword_status (for pausing/enabling) or google_ads_add_negative_keywords (for blocking queries). The only usage-related note is the confirm_delete requirement, which is an invocation guardrail rather than a selection criterion.

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