Pause Keyword (gated mutation)

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

Annotations already mark destructiveHint=true and readOnlyHint=false; the description adds that this is gated and requires explicit user consent and acts on a single criterion. This context is useful and does not contradict the annotations.

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 terse sentences deliver the core action first and the gating requirement second, with no repetition of schema or annotation details. Every sentence earns its place.

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 gated mutation with a true destructive annotation, the description provides the essential permission and consent prerequisites. Required IDs are documented in the schema, and an output schema exists, so no critical behavior is left unaddressed.

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?

The description highlights the most identity-critical parameter (criterion_id) and clarifies the otherwise opaque explicit_user_intent boolean by tying it to the gate. Customer_id and ad_group_id are covered in the input schema, and response_format has an enum, so the description compensates for moderate schema coverage.

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 names a specific verb ('Pause'), a specific resource ('a single keyword') and the identifying field ('criterion_id'), which distinguishes it from siblings like pause_campaign and resume_keyword. The title's 'gated mutation' is reinforced by a clear action statement.

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?

It clearly states the gating precondition (GOOGLE_ADS_ALLOW_MUTATIONS + explicit_user_intent) and instructs 'Ask the user first.' It doesn't enumerate alternatives or exclusions, but the gate and command make the intended call flow unmistakable.

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