mailveri_delete_batch

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: a server-side rejection rule for queued/processing jobs and the remediation path, which lets an agent avoid a guaranteed error. It stops short of saying the deletion is irreversible or what the response contains, but the output schema covers returns.

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 short sentences: the action and scope first, then the blocking constraint and remediation. Every clause carries information an agent needs, with no restatement of the tool name or annotations.

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 one-parameter destructive tool with an output schema and rich annotations, the definition covers purpose, precondition and failure mode adequately. The remaining gap is the job_id source/format, which leaves the agent without a stated way to acquire the required input.

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 0% and there is one required parameter (job_id) whose format and provenance are never explained. The description only implies that some job is targeted and does not say where the agent obtains the ID (e.g., from a verify or status call) or what form it takes, so it fails to compensate for the schema gap.

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 gives a specific verb (delete) plus a precisely scoped resource (a finished or canceled bulk email verification job in your account), and explicitly excludes jobs in other states. An agent can distinguish this from the sibling read/status/submit tools without opening any schema.

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 clearly states the precondition for use (job must be finished or canceled) and what to do when that precondition fails: wait, or cancel via the MailVeri dashboard first. It does not name an in-toolset alternative, but no sibling performs deletion, so the guidance is effectively complete for this operation.

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