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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no read/write profile, no auth or rate-limit notes, no cost model, and no indication of what 'free' refers to or what the call produces. The phrase 'free discovery utility' is not enough to characterize behavior.

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?

It is short, but brevity here reflects under-specification rather than efficiency — the single fragment contains no actionable content. Nothing is front-loaded because nothing meaningful is stated at all.

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 no annotations, no output schema, and no parameters, the description is the only source of information about this tool, and it supplies none. An agent cannot determine what the tool does, what it returns, or when to invoke it.

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?

The input schema declares zero parameters, so there is no parameter semantics for the description to add. Per the rubric, a 0-parameter tool takes the baseline of 4; the gap here lies elsewhere, not in parameter documentation.

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 'R/IV free discovery utility' is a cryptic fragment of jargon that never states a verb or resource. 'R/IV' is undefined and 'discovery utility' does not tell an agent what the tool returns, despite the name implying price quoting. It neither distinguishes itself from the 30+ verify/monitor siblings nor clarifies its own purpose.

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?

There is no when-to-use, when-not-to-use, or alternative guidance of any kind. With siblings like quote.verify, transaction.verify, and vendor.diligence present, the agent has no basis for choosing this tool over them.

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