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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety bar is low. The description adds useful context beyond that: default ordering (most recent first as NeverBounce returns them), the field set returned, and the underlying POST /jobs/search endpoint. It does not mention rate limits or pagination behavior explicitly, keeping it from a 5.

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?

Effectively two sentences with the resource and ordering front-loaded, followed by the filterable fields. The long parenthetical list of result totals is slightly dense but each item is informative rather than 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?

There is no output schema, so the description's enumeration of returned fields (id, status, filename, timestamps, totals, bounce estimate, percent complete) is genuinely necessary and present. Pagination params are covered by the schema; only per-call behavioral details like rate limits are absent.

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 100%, so all five parameters are documented at the schema level. The description echoes the filterable fields (id, exact filename, status) but adds no new syntax or semantics, and does not mention page or items_per_page. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly identifies the resource (bulk verification jobs of the account) and the scope (list/search with filters), and enumerates returned fields. It stops short of naming a sibling for contrast, though the 'list of jobs' framing is distinguishable from neverbounce_get_job by implication only.

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 states 'Filter by id, exact filename or status,' which tells the agent how to narrow results but not when to choose this over neverbounce_get_job or neverbounce_get_job_results. Usage is implied (browse jobs) rather than explicitly bounded.

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