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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether removal is reversible, whether removal fails if a named group is absent, whether targeting data/history is lost, or whether the campaign must be paused first.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is part of why behavioral gaps remain.

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 destructive, open-world mutation with no output schema, the description should explain consequences and error conditions. With only two parameters fully documented in the schema, the missing piece is exactly the behavioral context an agent needs before invoking a destructive call.

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%, including an example for the nested channel_target_groups map, so the schema carries the burden. The phrase 'one or more channels' adds a mild clarification that the map is multi-channel, but no format or constraint details 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 gives a specific verb (remove) and a specific resource (targeting groups) plus scope (one or more channels in an existing campaign), so the operation is unambiguous. It stops short of distinguishing itself from siblings such as remove_audiences_from_campaign or remove_channels_from_campaign, which an agent must infer on its own.

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?

There is no explicit guidance on when to use this versus the other remove_* tools or the corresponding add tools. The only hint is 'in an existing campaign', which implies a campaign must already exist but is never stated as a prerequisite or exclusion.

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