pause_keyword

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

Since no annotations are provided, the description must disclose behavior. It does so by stating 'Previews unless confirm=true', indicating a dry-run default and actual mutation only with confirm. However, it omits details about permissions, error handling, or effects on already paused keywords.

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?

Extremely concise: two sentences with no wasted words. Each sentence adds distinct value—action definition and behavioral nuance. Structure is front-loaded with the primary purpose.

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?

Given the existence of an output schema and the simplicity of the tool, the description covers the core action and key behavior (preview). However, it fails to describe the required ID parameters or mention any edge cases (e.g., already paused keywords), leaving moderate gaps.

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?

With 0% schema coverage, the description should compensate. It only explains the confirm parameter (preview vs confirm). The three required parameters (customer_id, ad_group_id, criterion_id) receive no description, leaving their meaning entirely to the user's assumed knowledge.

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 the action 'Pause a keyword' and specifies the resource type as 'ad group criterion'. The parenthetical distinguishes it from pausing other entities like ads or ad groups, aligning with sibling tool names.

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 explicit guidance on when to use this tool over alternatives like pause_ad_group or pause_campaign. The description mentions a preview mode but does not clarify how confirm=true vs false relates to usage scenarios or provide context for decision-making.

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