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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description adds meaningful context: queued emails stay queued and resuming continues exactly where it left off, and other campaigns are unaffected. It does not cover edge cases like double-pausing, but the core behavior is well disclosed.

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?

The description is two sentences, front-loaded with the action, and contains zero filler. Every phrase earns its place: stopping sends, staying queued, resume continuity, and global scope of other campaigns.

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 simple mutation tool with one parameter, no output schema, and clear annotations, the description is complete. It explains the state change, the preserved queue, and the scoping to one campaign. No critical information is missing for an agent to understand the tool's effect.

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 schema already fully documents the only parameter (campaign_id: 'Campaign id to pause'), achieving 100% schema coverage. The description adds no additional meaning about the parameter beyond the fact it identifies 'one campaign', which is already implied. Baseline 3 is appropriate.

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 clearly states a specific action ('Pause one campaign') and explains the exact behavior (queued emails stop sending but stay queued). It distinguishes itself from sibling tools like outreach_resume_campaign and outreach_launch_campaign by emphasizing the pause semantics and continuity upon resume.

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?

Provides clear context for when to use: when you need to pause a single campaign while preserving its queue. It implies the use case for resuming later, but does not explicitly compare with alternatives (e.g., launch or delete). The sibling names help, but the description could be more explicit about when not to use it.

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