verify_emails_bulk

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

Annotations indicate the operation is not read-only, but the description adds genuinely useful context: the call is asynchronous, returns a batch id, and requires polling for the final result. This goes beyond the annotations and helps the agent understand the interaction model.

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 tightly packed sentences communicate scope, limit, asynchronicity, and the follow-up tool with no filler. Every word earns its place.

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 single-parameter async tool with no output schema, the description covers the essential workflow: provide emails, get batch id, poll the result tool. It could add minor details about error or polling behavior, but nothing critical is missing for correct invocation.

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 schema only documents 'emails' as an array of strings, so the description adds meaningful parameter semantics by specifying the 5,000-per-batch limit and clarifying the bulk, asynchronous nature of the request.

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 clear action ('Verify multiple email addresses in bulk') and differentiates itself from single-verification and result-polling siblings by specifying batch size and asynchronous behavior. This lets an agent immediately distinguish verify_emails_bulk from verify_email and get_verifications_bulk_result.

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 explicitly says to poll get_verifications_bulk_result after receiving a batch id, which gives a concrete next step. It also implies the single-email alternative by saying 'multiple' and 'bulk', though it does not explicitly name verify_email as the tool for one-off verification.

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