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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only that 'pending sends' are affected, but does not say whether disabling is reversible, whether already-queued/expired sends are touched, or what state the campaign schedule ends up in — meaningful gaps for a destructive mutation.

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?

One short, front-loaded sentence with no filler, but it is under-specified rather than concise — brevity here comes at the cost of the information needed to invoke a destructive, heavily-parameterized tool.

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?

With a nested-object schema, zero parameter documentation, destructive semantics, no output schema, and several competing sibling tools, a single sentence leaves the agent without the information required to call this correctly or safely.

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 single body parameter is a nested EmailSchedule object with ~11 properties (campaign_id, team_id, pause, asap, only_manual, follow_up_only, datetime, timezone, etc.) at 0% schema description coverage. The description explains none of them, so the agent cannot tell which fields matter for a disable operation versus a schedule/pause operation.

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 verb+resource combination ('disable' + 'pending sends for your campaign') is clear enough to know what happens. However, it gives no differentiation from close siblings like pause_campaign_schedule or cancel_upcoming_send, which an agent must choose between when scheduling is involved.

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 guidance on when to use this instead of pause_campaign_schedule or cancel_upcoming_send, and no prerequisites or preconditions are stated. The agent must infer the distinction from tool names alone.

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