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

Adds real value beyond the annotations: the cost model ('SPENDS 1 CREDIT PER EMAIL') is a consequential, irreversible side effect that matters especially given destructiveHint=true, and 'asynchronous' plus 'Returns the job id' tells the agent this is fire-and-poll, not a synchronous result. It doesn't say whether the job can be cancelled or what happens to credits on failure, which keeps it from a 5.

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?

Three short clauses, zero filler, and the highest-stakes fact (credit spend) is capitalized and front-loaded after the action. Nothing that could be cut without losing information.

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?

Covers action, cost, async semantics, and that an id comes back — enough to call it correctly despite the absence of an output schema. It stops short of pointing at the follow-up tools (get_batch_status / get_batch_results) that the returned id is for.

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 100%, so both parameters are already documented, and the description adds little: it reinforces that emails is the payload but is silent on webhook_url and any per-request email cap or format constraints. Baseline 3 applies when the schema carries the detail.

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?

A specific verb plus resource — submitting a list for asynchronous verification — with the endpoint named. It implicitly separates itself from the single-address sibling verify_email via 'batch' and 'list', but never names an alternative, so the differentiation is inferential rather than explicit.

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?

'For asynchronous verification' implies usage but never states when to prefer this over verify_email, nor any prerequisites such as list size limits or account credit balance. With no explicit when/when-not guidance, an agent must infer the choice from the word 'batch' alone.

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