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

The description adds substantial behavioral context beyond the annotations: it explains that keywords and ads stop serving, that the operation is irreversible, and that Google Ads sets status=REMOVED rather than truly deleting, with recovery only by recreating everything from scratch. These details directly support safe invocation of a destructive operation.

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 front-loaded with the core action and consequence, then provides the irreversibility warning and alternatives. Every sentence adds useful decision-making context, with no filler.

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 rich annotations, a fully documented input schema, and no output schema, the description provides the necessary behavioral context: consequences, irreversibility, and alternatives. Nothing an agent needs to safely call this destructive tool is missing.

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 100%, with both parameters documented in the input schema, including the confirm flag and adGroupId. The description does not add syntax or format details for these parameters, so it meets the baseline of 3 when the schema already carries parameter meaning.

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 ('Permanently remove an ad group from a live Google Ads campaign') and clearly distinguishes the action from sibling tools like pause_campaign and remove_keywords. An agent can immediately understand the operation and its scope.

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 explicitly names alternatives (pause_campaign for whole-campaign pauses, remove_keywords for specific keywords) and gives the condition for using this tool instead: only when a whole thematic block of the campaign needs to go. Exclusions and alternatives are fully specified.

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