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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/non-repeatable profile is covered structurally. The description adds essentially nothing beyond that: it does not disclose that this is an asynchronous job, how results are returned, credit cost, or rate limits — all important for a batch mutation.

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 front-loaded sentence with no filler, but it is so terse that it functions closer to a title than an instruction and omits the batch-size constraint that the schema imposes.

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 an asynchronous batch submission with no output schema and a nested 1000-item array, the description should convey what is returned (e.g., a batch identifier) and how to collect results. Neither is present, leaving a significant gap an agent needs to call this 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?

Schema description coverage is 100% — the nested full_name/domain fields are documented and explicitly cross-reference the single find-email endpoint's semantics. The description adds no parameter meaning of its own, so the baseline 3 is appropriate.

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?

States a specific verb (submit) and resource (bulk find-email batch), which is clearly distinguishable from the singular contacts-enrich_work_email. It does not, however, contrast itself with the sibling contacts-enrich_work_email_batch_get that presumably retrieves results, so the batch lifecycle is not made 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?

No guidance on when to prefer batching over the single find-email endpoint, how many contacts to submit, or that results must later be fetched via contacts-enrich_work_email_batch_get. The word 'bulk' implies scale but offers no threshold or conditions.

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