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

With no annotations provided, the description carries the burden and usefully discloses the main side effects: hunters restart and linked outreach resumes. It does not cover permissions, idempotency, error cases, or response behavior, so it is strong but not fully complete.

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 a single front-loaded sentence with no wasted wording. The parenthetical clarification earns its place by preventing confusion about separately paused outreach.

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 core state transition is well covered, including the important exception for separately paused outreach. However, with no annotations, no output schema, and an undocumented id parameter, the definition still leaves the agent without key input and result context.

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?

There is one required parameter, id, with 0% schema description coverage, and the description never explains that it identifies the paused SDR search. The parameter is therefore left semantically undocumented.

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 and resource: it resumes a paused SDR process. It also clarifies exactly what restarts, namely hunters and outreach that was paused together with the search, which distinguishes it from separate resume tools for hunters or 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?

It clearly indicates this tool applies to a paused SDR process and explains the key boundary: separately paused outreach remains paused. It does not explicitly name sdr_resume_hunter or sdr_resume_outreach as alternatives, but the scope is sufficiently clear for selection.

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