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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description should explain what is actually destroyed or held: whether queued sends are cancelled permanently, whether the pause is reversible, and whether permissions are needed. It only says 'pending sends' are paused, which mildly narrows the blast radius but leaves the destructive semantics unexplained.

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 short sentence with zero filler and the action front-loaded. It is efficient, though the brevity is under-specification rather than disciplined concision.

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 with an 11-field nested body, no output schema, and several semantically overlapping siblings, the description leaves nearly everything an agent needs unanswered. It does not explain the effect on already-queued sends, reversibility, or the required identifiers.

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 0% and the single 'body' parameter expands into an 11-field nested EmailSchedule object (campaign_id, team_id, pause, asap, datetime, timezone, entity_id, only_manual, follow_up_only, start_timestampz). The description mentions none of these; 'for your campaign' weakly hints at campaign_id but leaves the other ten fields, including which control the pause behavior, undocumented.

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 and resource ('Pause pending sends for your campaign'), which is far clearer than the bare tool name alone. However it never differentiates itself from close siblings like disable_campaign_schedule or cancel_upcoming_send, whose semantics an agent would need to distinguish before choosing.

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 versus disable_campaign_schedule, cancel_upcoming_send, or reschedule_upcoming_send, nor on prerequisites such as an existing schedule. The usage has to be inferred entirely from the name and the phrase 'pending sends'.

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