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

Annotations already declare readOnlyHint=true. Beyond that, the description adds real behavioral context: results are paginated, ordered newest-first, and the call requires an API key (auth requirement). It does not describe what fields come back, but with annotations covering the safety profile this is solid added value.

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 tight sentences, zero waste, with the core list scope and ordering front-loaded before the optional filter and auth note.

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 read-only paginated list tool with no output schema, the description covers ordering, pagination, filtering, and auth. The remaining gap is the shape of returned job records, which an agent might want when deciding between this and get_bulk_job.

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%, so the description must carry the parameter burden. It mentions the optional status filter and that results are paginated (covering page/page_size conceptually), but gives no valid status values, no page-size limits, and no default behavior recovery.

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 (List) and resource (bulk verification jobs) plus scope details: recent, paginated, newest first. It implicitly separates itself from get_bulk_job and submit_bulk_verification, but never names a sibling explicitly.

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?

"Optionally filter by status" and "Requires an API key" imply usage context, but the description never states when to use this list tool versus get_bulk_job for a single job or cancel_bulk_job. No exclusions or alternatives are given.

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