remove_campaign

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

Beyond the annotations, the description discloses that this is a soft-delete, that the campaign status becomes REMOVED, and that confirm_removal must be True. This adds meaningful behavioral context beyond the structured destructiveHint and readOnlyHint 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?

The description is compact and front-loaded, with the core action stated first, followed by a warning and a concise parameter list. Every sentence contributes essential operational information without redundancy.

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 three-parameter destructive operation with annotations already covering safety and idempotency, the description is nearly complete. It does not mention return values or side effects on child entities, but the lack of an output schema makes that less critical.

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 description coverage, the Args section compensates by explaining customer_id as the Google Ads customer ID, campaign_id as the campaign to remove, and confirm_removal as a required safety flag. It does not add format details, but it provides enough semantic meaning to use the tool correctly.

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 opens with 'Soft-delete (remove) a campaign,' which names a specific verb, resource, and mode. It further clarifies the behavior by stating the campaign will be set to REMOVED status, clearly distinguishing this from update_campaign and set_campaign_status.

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 clearly labels the operation as destructive and explains the confirm_removal safety gate, providing strong guidance on when the tool should be invoked. It does not explicitly compare against alternatives like set_campaign_status, but the purpose is unambiguous enough that an agent can infer correct usage.

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