mailveri_delete_batch

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

With no annotations, the description carries the full behavioral burden, and it does not disclose that this is destructive, whether it is reversible, whether results are recoverable after deletion, or any auth/permission requirements. For a deletion tool with zero annotation coverage, this is a substantial gap.

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?

One short sentence with no filler, and the operation is front-loaded. It is efficient, though the 'cancel or delete' hedge adds minor ambiguity rather than precision.

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?

An output schema exists, so return values need not be described, but a destructive operation with no annotations, no reversibility/permission context, and an undocumented parameter is under-specified for safe 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?

Schema coverage is 0% for the single required job_id, and the description adds no format, source, or constraint information about it. The name is fairly self-explanatory, but neither schema nor description explains where a valid job_id comes from (presumably a prior verify_batch call).

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+resource: 'Cancel or delete a bulk email verification job'. This clearly distinguishes it from siblings like mailveri_verify_batch, mailveri_get_batch_status, and mailveri_download_batch_result. The dual verb 'cancel or delete' is slightly imprecise about which semantic applies, but the operation is unambiguous.

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 versus alternatives (e.g., check mailveri_get_batch_status first), no prerequisites, and no indication that this is irreversible or what happens to in-flight jobs. The agent is left to infer usage entirely.

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