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

Goes well beyond the annotations: discloses that credits can be spent, that execution is asynchronous, that the job may continue even if the response is lost, and the mitigation (check the dashboard before resubmitting). These are exactly the non-idempotent, side-effecting traits an agent needs before calling a job-creating tool.

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?

Four tight sentences, front-loaded with the core action and its credit cost, then the confirm gate, then the resubmission warning. No filler.

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?

With no output schema, the description partly compensates by pointing to reoon_bulk_results for results, but never states what the create call itself returns (e.g., a job identifier) and omits the `name` parameter. Otherwise complete for a credit-spending async job tool.

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 0%, so the description carries weight: it explains the confirm:true gate (whose schema default false is otherwise unexplained) and the 10–1,000 email bounds. However, the `name` parameter is never mentioned, leaving one of three params undocumented in both schema and description.

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'), resource (10–1,000 emails), and mode (asynchronous POWER verification), plus that it starts a vendor job. The closing sentence differentiates it from sibling reoon_bulk_results, which reads results rather than creating the job.

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?

Gives concrete operational guidance: requires confirm:true, check the dashboard before resubmitting, and results are retrieved via reoon_bulk_results. It does not explicitly contrast with the synchronous sibling reoon_verify_email, so the routing advice is clear but not complete.

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