keyword_pause_preview

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is a preview rather than an actual pause, but it does not explain what previewing entails or how the preview is later applied.

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 wasted words. It is efficiently structured, though its brevity contributes to gaps handled in 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?

For a simple preview tool with annotations and an output schema, the description is minimally adequate. However, given the surrounding preview/apply workflow, it should clarify that this only previews the pause and does not itself apply the change.

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 moderate at 67%; profile and adAccountId are documented in the schema, while id is undocumented there. The phrase 'one targeting keyword' implies id refers to a keyword, but the description adds little further meaning beyond the schema.

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 and resource: preview pausing one targeting keyword. The word 'targeting' distinguishes it from negative-keyword tools, and 'pausing' distinguishes it from sibling keyword resume, delete, update, bid, and create previews.

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 description only restates the operation and gives no explicit when-to-use guidance, exclusions, or alternatives such as how this relates to operations_apply or other keyword preview tools. Usage is implied at best.

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