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

The description adds meaningful behavioral context beyond the title by noting the action is 'Reversible' and that it only stops 'new messages.' However, with no annotations, the description carries the full disclosure burden and does not mention side effects such as what happens to already-queued messages, whether the operation is idempotent, or what response to expect.

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 extremely concise: a single action sentence followed by a one-word reversibility note. It is front-loaded and contains no filler, making it easy for an agent to parse quickly.

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 one-parameter tool with no output schema, the description covers the core action and reversibility. However, it lacks guidance on when to use it versus related pause tools, and it leaves the search_id parameter semantics underspecified, so the overall context is adequate but incomplete.

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 provides no description for search_id, and the description only vaguely refers to 'this SDR campaign.' It does not clarify how to obtain the search_id, whether it identifies an outreach campaign versus a search, or what value format is expected. With 0% schema coverage, the description should compensate but does not.

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 states a specific verb ('Stop sending new messages') and a resource ('this SDR campaign'), which clearly conveys the tool's function. The title reinforces this with 'Pause SDR outreach delivery.' However, it does not explicitly differentiate itself from closely related siblings like sdr_pause_search or pause_campaign, so it falls just short of a 5.

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?

The description gives no guidance on when to use this tool versus alternatives such as sdr_pause_search, pause_campaign, or sdr_delete_outreach. It also does not mention that sdr_resume_outreach is the counterpart for reversing the pause. Without explicit usage context, an agent must infer when this tool is appropriate.

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