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

The description mentions a state change ('clear paused state') and an action ('restart all hunters'), but does not elaborate on side effects, such as whether the search starts from scratch or continues from a checkpoint. It gives a basic transparency of the operation but omits important behavioral details.

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 concise sentence that directly states the main action. It is well-structured and front-loaded, avoiding unnecessary words or complexity.

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 lacks essential context: it does not explain the id parameter, describe expected outputs, or mention any prerequisites or error conditions. Given the simple schema and no output schema, the missing explanation of the parameter makes the tool incomplete for a user to understand how to invoke it correctly.

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 sole parameter 'id' is not described at all. The description provides no context for what the id refers to (e.g., search ID, campaign ID). The schema offers zero descriptive coverage, leaving the parameter's meaning completely ambiguous.

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 clearly states the action: 'Clear paused state and restart all hunters.' It is explicit about resuming a paused search, though the term 'hunters' is somewhat ambiguous. Overall, it effectively communicates the tool's primary purpose.

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 does not provide explicit guidance on when to use this tool versus other resume-related tools like sdr_resume_outreach. It implies usage for paused searches but lacks context on prerequisites or alternatives.

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