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

With no annotations, the description carries the full burden. It does disclose two useful traits beyond structured data: execution is paid, and a completed run returns an RVO plus a signed verification receipt. However, it omits auth requirements, failure/unpaid behavior, cost, and any rate limits.

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?

Only two sentences, so it is not bloated, but the first clause redundantly restates the tool name ("R/IV procurement.evidence —") and leans on undefined acronyms (R/IV, RVO), spending words without adding information. The genuinely useful fact (paid, returns a signed receipt) is buried in the second sentence.

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 zero-parameter tool with no output schema and no annotations, the description must carry the explanation of returns and behavior. It gestures at the output (RVO + signed receipt) but never defines RVO, and gives no sense of when the tool applies versus its numerous siblings.

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 tool takes zero parameters and schema coverage is 100%, so the baseline is 4. The description correctly implies no input is required, and there is nothing further a parameter section could add.

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 names a domain and a vague action ("evidence-verification primitive for enterprise assurance") but the jargon "primitive" and "R/IV" obscure what the tool actually does. It also fails to differentiate from the many nearby verification siblings (evidence.bundle, evidence.monitor, citation.verify, vendor.diligence), leaving the agent to guess its niche.

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 explicit when-to-use guidance, no when-not-to-use, and no named alternative among the ~34 sibling verification tools. The only implicit usage cue is "completed paid execution," which hints at a prerequisite but does not tell the agent when this tool is the right choice.

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