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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds non-annotation context: zero cost, owner-scoped visibility, and cursor-termination behavior — genuinely useful traits beyond the structured fields.

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 front-loaded clauses, no filler, purpose stated before the operational caveats. It is arguably under-specified rather than padded, so conciseness itself is fine.

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 an output schema present, return values need not be explained, and annotations cover safety, so the remaining burden is modest. The description covers cost, scope and pagination; the only real omission is sibling disambiguation among the several status/lookup tools.

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 must carry all three parameters and it does not. It explains cursor iteration (as 'next_cursor', which does not match the schema's 'cursor' field name) but says nothing about limit's cap or job_id's meaning, and the naming mismatch risks confusing an agent.

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 fragments 'Free, owner-scoped stored results' plus 'never re-submit a completed job' identify this as the retrieval side of the job lifecycle, implicitly contrasted with vri_submit_job. It stops short of an explicit verb and does not differentiate from other status/result readers such as vri_operation_status or vri_bulk_status.

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 instructions ('Follow next_cursor until null', 'never re-submit a completed job') and a cost signal ('Free'), which is useful when-versus-when-not context. However it never says when to call this instead of sibling status tools, leaving selection to inference.

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