Hunter Enterprise Batch Create

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

With no annotations provided, the description must disclose behavioral traits. It only states the action (create task) but omits details like synchronous/asynchronous behavior, task lifecycle, rate limits, or what happens after creation. The parameter descriptions hint at some constraints (e.g., search_type limits) but the description itself lacks transparency.

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?

A single sentence encapsulates the core purpose with no extraneous words. It is front-loaded and efficiently communicates the tool's function.

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?

Given 10 parameters, no output schema, and no annotations, the description is too brief. It fails to explain the return value, how to monitor task progress, or the relationship with batch download/pull tools. More context about the batch workflow is needed for effective use.

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 100% with each parameter having a description. The description adds minimal value beyond the schema—only hinting at two modes (query vs CSV). Baseline 3 is appropriate as the schema already documents parameter meaning.

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 it creates a batch search task using either a query or CSV upload. This distinguishes it from sibling tools like hunter_enterprise_search (direct search) and batch download/status tools. The verb 'Create' and resource 'batch search task' are specific.

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 guidance on when to use this tool versus alternatives such as hunter_enterprise_search or hunter_personal_batch_create. The description does not mention prerequisites, limitations, or context for choosing between query and file upload modes.

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