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 known; the description adds nothing beyond that. It never says whether the removal is immediate/irreversible, whether the campaign must be live or paused, or what happens if an offer name or channel key doesn't exist.

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?

It is short, but the sentence is broken into fragments with misplaced periods ('Remove offers. Lead Gen forms OR Landing Pages. from one or more channels...'), which hurts front-loading and readability. The core verb and resource are still first, so it is not wasteful, just sloppy.

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 mutation taking a nested map with no output schema, the description should disclose result behavior (partial success, unknown keys, per-channel outcomes) and preconditions. Those gaps leave the agent under-informed about consequences of the 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% and the channel_offers map already includes an explicit example and per-key array constraints, so the schema carries the load. The description only restates that offers are Lead Gen forms or Landing Pages and that multiple channels may be targeted, without adding format or edge-case guidance for the nested map.

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?

States a specific verb (remove) and resource (offers of Lead Gen form / Landing Page type) scoped to channels of an existing campaign, so the operation is unambiguous. It does not name or contrast with the closely related siblings (remove_audiences_from_campaign, remove_target_groups_from_campaign, remove_channels_from_campaign), leaving that distinction implicit.

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 when-to-use, prerequisites, or alternatives are given. The agent must infer from the name alone whether this is the right removal tool versus remove_channels_from_campaign or remove_target_groups_from_campaign.

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