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

With no annotations, the description carries the full behavioral burden. It does disclose two genuinely useful facts absent from structured data: execution is 'paid' (a cost implication) and a completed run returns an 'RVO plus signed R/IV Verification Receipt.' However, it omits auth requirements, rate limits, and what happens on partial/failed execution.

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?

Two sentences, so nothing bloated, but the first clause redundantly restates the tool name and the second is dense with unexplained jargon. Short but not well front-loaded in terms of actionable meaning.

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?

No output schema, no annotations, no parameters, yet the description leaves the return artifact ('RVO', 'Verification Receipt') undefined and gives no context on how this primitive fits relative to sibling verification tools. Inadequate for a tool whose value is entirely behavioral.

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, so parameter semantics baseline is 4. There is nothing for the description to clarify beyond what the empty schema already conveys.

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 itself an 'independent evidence-verification primitive for retrieval reconstruction,' which gestures at a verification function but never explains what 'reconciling a timeline' actually does. Terms like 'RVO' are undefined, and with 30+ verification siblings (citation.verify, source.verify, provenance.receipt, etc.) there is no differentiation. Purpose is implied but opaque.

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?

No when-to-use guidance, no prerequisites, and no named alternatives despite a crowded landscape of near-identical verification tools. The agent gets no basis for choosing this over claim.check or transaction.verify.

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