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

Annotations only flag readOnlyHint=false, idempotentHint=false and openWorldHint=true; the description goes well beyond them by disclosing that each number is a fresh paid read, that a spend scope is required, that live customer keys draw on balance, that repeating a call can charge again, and how request_id converts a repeat into a safe retry. This is exactly the cost/idempotency behavior an agent needs before invoking a billable open-world tool, and it is consistent with the annotations rather than contradicting them.

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?

The purpose and batch limit are front-loaded, followed by cost, retry and testing guidance in short declarative clauses with no filler. The telegraphic style ('Live customer keys spend balance') is dense but every sentence carries a distinct operational fact.

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 values need not be described, and the description covers the critical unknowns for a billable bulk tool: spend scope, re-charge risk, retry safety, cost capping and test keys. The remaining gap is sibling routing — nothing tells the agent when to prefer vri_number_lookup, vri_quote or vri_spam_check instead.

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 100%, so the schema already documents phone_numbers, products, max_cost and request_id thoroughly, and the baseline is 3. The description largely restates the schema's cost-cap and request_id semantics ('Use max_cost to cap the quote', 'reuse a stable request_id with identical arguments'), adding only the retry-charge linkage that the schema implies, so there is little net-new parameter meaning.

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 and resource ('Live lookup'), the batch ceiling (up to 100 North American phone numbers in one call) and the returned data sets (carrier, line type, routing, optional cnam/spam/messaging). It clearly reads as the bulk counterpart to the sibling vri_number_lookup, though it never names that sibling explicitly, so differentiation is inferred from 'bulk'/'up to 100' rather than stated.

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 gives actionable operational context: use max_cost to cap the quote, use a test key for integration tests, and reuse request_id with identical arguments for a safe retry. What it does not provide is an explicit when-not or a named alternative (e.g. vri_number_lookup for a single number, vri_quote for pricing only), which keeps it short of a 5.

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