negative_keywords_bulk_update_preview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds useful constraints beyond annotations: the 100-item maximum and the single-scope limitation. It does not explain return behavior, but the output schema likely covers that.

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 a single front-loaded sentence with no filler. The limit and scope are stated immediately, making it efficient for an agent to parse.

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?

This is a bulk mutation-preview tool with five parameters, nested item objects, and only 40% schema description coverage. The one-sentence description leaves important gaps around parameter roles, item structure, and when to use this preview versus related tools, even though annotations and the output schema reduce some burden.

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 40%, and the description does not compensate by explaining the required profile, adAccountId, items array, or the campaignId/adGroupId scope parameters. 'One scope' hints at campaign or ad group scoping but does not clarify which parameters define it or how items are structured.

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 verb ('Preview'), resource ('negative keyword updates'), quantity limit (up to 100), and scope, making the operation understandable. It does not explicitly distinguish itself from siblings like negative_keyword_update_preview, keywords_bulk_update_preview, or negative_keywords_bulk_create_preview, so it falls short of 5.

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 word 'Preview' implies a dry-run use case, but the description gives no explicit guidance on when to use this bulk preview versus the single negative_keyword_update_preview or the bulk create preview. It also does not mention prerequisites, follow-up apply steps, or when not to use it.

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