keywords_bulk_update_preview

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description does add non-obvious context—the 100-item ceiling and the notion of a single atomic operation—but 'drift-bound' is undefined jargon that the agent cannot act on, and nothing explains whether the preview expires or must be followed by an apply step.

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?

A single front-loaded sentence with no filler; the batch limit and atomicity claim both land immediately. Nothing could be cut without losing information.

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?

An output schema exists, so return values need no explanation, and the annotations cover safety. For a bulk mutation-preview tool the remaining gap is workflow: 'drift-bound' is unexplained and the agent is not told whether the preview must be applied via operations_apply.

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 50%, with adGroupId and the items/bid structure undocumented. The description's 'up to 100' actually adds a real constraint the schema does not enforce (no maxItems), which is valuable, but it says nothing about the per-item id/bid/status/correlationId semantics that make up the bulk payload.

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?

States a specific verb (Preview) and resource (targeting keyword updates), plus two concrete qualifiers: a batch cap of 100 and single-operation semantics. It doesn't explicitly name how it differs from keyword_update_preview or keywords_bulk_create_preview, but 'bulk' and 'updates' make the distinction inferrable.

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?

Usage is only implied by the words 'bulk' and 'Preview'; the description never says when to pick this over keyword_update_preview for a single edit, nor when to pick it over keywords_bulk_create_preview. No prerequisites or exclusions are stated.

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