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

With no annotations, the description carries the burden fully. It usefully discloses that only the targeted hunter stops while others continue, and that the action is reversible — two real behavioral facts. It is silent on permissions, effect on in-flight runs, and what a paused hunter stops doing.

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, front-loaded with the scope-defining clause and followed by the reversal path. No waste.

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 two-parameter mutation with no output schema and no annotations, it covers the core effect and reversibility, but omits what a paused hunter means operationally and gives no hint about the undocumented search_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 coverage is 50%: 'source' is documented and points to sdr_list_hunters, but 'search_id' has no description anywhere. The description adds nothing about either parameter, so it does not compensate for the gap.

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?

Specific verb (pauses) + resource (one hunter of a search) with explicit scope: 'the others keep running'. This implicitly but clearly differentiates it from search-level siblings like sdr_pause_search.

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?

Names the counterpart action (sdr_resume_hunter) for reversal, which helps an agent understand lifecycle, but gives no explicit when-to-use vs sdr_pause_search or sdr_pause_outreach guidance.

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