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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description still adds real value by disclosing cost ('Free') and a non-obvious operational constraint about not resubmitting pending work with a new ID.

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?

A single dense sentence that front-loads the cost signal and the usage trigger with zero filler. It is perhaps terse to the point of omitting needed detail, but nothing is wasted.

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-value explanation is unnecessary, and annotations cover the safety profile. Still, for a tool whose entire contract is 'pass an operation ID', the description says nothing about acquiring that ID, which is the main completeness gap.

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 operation_id is undocumented in both the schema and the description. The description never explains what an operation ID is or where the agent obtains it, leaving the sole parameter's semantics entirely unexplained.

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 recognizable verb+resource ('check an operation') with a specific condition ('after an interrupted call'). However, it does not distinguish this from siblings like vri_bulk_status or vri_job_results, which all sound like status-checking tools; the agent must guess from the name alone which one applies.

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 when-to-use context ('after an interrupted call') plus an important behavioral rule ('pending work must not be resubmitted with a new ID'). It lacks explicit named alternatives, but the triggering scenario is clear enough to route an agent.

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