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

With no annotations, the description carries the full behavioral burden, yet it only hints that execution is 'paid' and yields a 'signed' receipt. It omits whether the call is read-only or mutating, cost/rate implications, authorization requirements, and the meaning of the unexplained RVO/R/IV artifacts.

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 (two sentences) and not padded, but it leads with an opaque acronym prefix rather than a clear action and leaves key terms undefined, so the brevity costs clarity rather than aiding it.

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 tool with no annotations, no output schema, and no parameters, the description is the only signal an agent has, and it is insufficient: the return value claim ('RVO plus signed Receipt') is described in undefined jargon and no invocation context is given.

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 (empty object schema), so there is no parameter semantics to communicate and the baseline of 4 applies. The description adds nothing here, but nothing is required.

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 labels the tool an 'independent evidence-verification primitive for provenance' and says it 'returns an RVO plus signed R/IV Verification Receipt,' but RVO and R/IV are never defined and no clear verb+resource action is stated (does it issue, retrieve, or verify?). It does not distinguish itself from siblings like evidence.bundle, source.verify, or transaction.verify beyond a vague 'provenance' label.

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 statement of when to use this tool versus the many sibling verify/audit tools, nor any prerequisites or exclusions. The only contextual hint is 'Completed paid execution,' which implies post-execution timing but is not framed as guidance.

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