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

No annotations exist, so the description carries the full behavioral burden. It does disclose one useful trait — execution is 'paid' and returns an RVO plus a 'signed R/IV Verification Receipt' — but 'RVO' and 'R/IV' are undefined jargon, and there is no word on failure modes, cost, idempotency, or what 'independent' verification actually entails.

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 short sentences, front-loaded, with no filler. The brevity is appropriate; the flaw is under-specification rather than verbosity.

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 output schema, no annotations, and zero parameters, the description is the only source of information — yet it leaves the return payload (RVO, receipt format), the invocation model for a parameterless call, and sibling differentiation entirely unexplained. It is not complete enough for confident selection or invocation.

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 per the rubric the baseline is 4. There is nothing for the description to clarify or compensate for on the input side.

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 largely restates the tool name: 'citation.verify' paired with 'evidence-verification primitive for verification' is circular, and the phrase 'for verification' adds nothing. It never states what a citation is being verified against or how this differs from source.verify, claim.check, quote.verify, or the other ~30 verification siblings.

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 guidance, no prerequisites, and no named alternative despite a namespace crowded with near-synonymous verify/check/audit tools. An agent has no basis for choosing citation.verify over source.verify or claim.check.

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