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

With no annotations provided, the description carries the full burden and does disclose key traits: 'Data is kept' (non-destructive) and 'Reversible with sdr_resume_search.' It does not address whether in-flight sends are cut off or what permissions are required, but the core mutation semantics are covered.

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, scope front-loaded, with zero filler. Every clause (whole process, both channels, data retained, reversal tool) earns its place.

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?

The description adequately explains the effect and reversibility of this pause mutation without annotations, but it leaves the lone parameter's meaning unaddressed for a tool with no output schema or annotation coverage. Adequate but with a clear gap around the id.

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 required 'id' parameter is never mentioned in the description. It is ambiguous whether the id identifies a search process or something else, so the agent must infer from the tool name alone.

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 the exact scope: pausing the whole SDR process, naming both components (every hunter AND all outreach sending via email and LinkedIn). This clearly distinguishes it from the partial siblings sdr_pause_hunter and sdr_pause_outreach.

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?

Implicitly routes the agent: this is the whole-process pause, contrasted against the narrower hunter/outreach pause siblings, and it names the reversal tool sdr_resume_search. It does not state explicit 'use this when...' conditions or exclusions, leaving that inference partly to the agent.

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