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 one useful trait — that a completed execution is 'paid' and returns an 'RVO plus signed R/IV Verification Receipt' — but it never says whether the operation is read-only or mutating, what it costs, what 'RVO' means, or what happens on failure.

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 and front-loaded, which is good, but the opening clause is wasted on restating the tool name and the phrase 'primitive for evidence' is redundant. The genuinely informative part (paid execution, receipt) is compressed into a jargon-heavy 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-param tool with no output schema and no annotations, the description should clarify the tool's role and return value. It only vaguely gestures at 'RVO' and a signed receipt without explaining either, leaving an agent unable to distinguish it from the 30+ sibling verification tools.

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 are no parameter semantics for the description to add or omit.

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 mostly restates the tool name with jargon: 'contradiction.scan' becomes an 'independent evidence-verification primitive for evidence,' which is circular and never says what it actually scans for or does with a contradiction. It hints at verification and a receipt, but the core verb+resource is not stated plainly enough to distinguish it from siblings like claim.check or source.verify.

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 guidance on when to use this tool versus the many alternatives (citation.verify, claim.check, evidence.bundle, source.verify, etc.). No prerequisites, no exclusions, no context of any kind.

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