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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety bar is lower. The description adds real but thin behaviour: it validates against existing campaign and pitch-limit checks, implying possible rejection. It omits what gets destroyed or overwritten, and how asap/pause/datetime interact.

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, which is good. But brevity here is under-specification rather than efficient compression — the sentence is small because it omits nearly everything.

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?

This is a destructive, open-world mutation with a nested ten-field body, 0% schema coverage, and no output schema. The description supplies only one clause about validation, leaving far too much of the calling contract to inference.

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 nested body carries ten cryptic fields (asap, pause, add_more, only_manual, follow_up_only, start_timestampz vs datetime), yet the description explains none of them. It gives the agent no way to know which fields are mutually exclusive or what defaults imply.

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 names a verb and resource (schedule campaign pitches) and hints that scheduling runs through existing checks. But it never says what 'schedule' produces — a fixed datetime send, an ASAP send, or a paused schedule — so an agent can't tell it apart from pause_campaign_schedule, disable_campaign_schedule, or reschedule_upcoming_send.

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?

It says nothing about when to call it versus the many neighbouring scheduling tools, or what prerequisites must be true. The only implied usage signal is 'existing campaign and pitch-limit checks', which is a precondition, not guidance on choice of tool.

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