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

No annotations are provided, so the description carries the full burden. It does add two genuine behavioral facts beyond the name: only *new* messages stop (existing/in-flight sends are not addressed) and the action is reversible. It omits permission requirements, whether the underlying search keeps running, and any effect on queued messages.

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?

Two short sentences, zero filler, with the action front-loaded and the reversibility guarantee appended. Nothing here is wasted.

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 state-changing, no-annotation, no-output-schema tool the description is too thin: it neither explains the required search_id nor differentiates from sdr_pause_search. The 'reversible' note is the only context that helps the agent act 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 parameter search_id has 0% schema description coverage and no enums, so the description must compensate — but it never names or explains the identifier. Referring to it loosely as 'this SDR campaign' does not tell the agent where to obtain a valid search_id.

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 clear verb+resource: 'Stop sending new messages on this SDR campaign.' An agent knows this halts outbound delivery and that it is reversible. However, it does not distinguish itself from the very similar sibling sdr_pause_search, and it calls the target a 'campaign' while the parameter is search_id, leaving the object of the action slightly ambiguous.

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?

No when-to-use or when-not-to-use guidance, and no mention of alternatives such as sdr_pause_search (to halt the underlying search) or sdr_delete_outreach (to remove outreach entirely). The agent must infer the routing from the name alone.

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