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

No annotations are provided, so the description carries the full burden. It does disclose two useful behavioral facts beyond structured data: execution is paid ("Completed paid execution") and it returns a signed "R/IV Verification Receipt" plus an RVO. However, it omits permissions, failure modes, and what an incomplete/unpaid execution yields, and the acronyms are never expanded.

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 compact sentences with the identity front-loaded and no padding. It is efficient, though the repeated "R/IV" prefix and unexplained acronyms slightly reduce signal density.

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 annotations, no output schema, and no parameters, the description is the only source of context and it remains opaque: RVO and R/IV are undefined, the return payload's shape is unspecified, and no prerequisites or failure behavior are given. It names output artifacts but does not make the tool callable with confidence.

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 the schema is trivially complete, so there is nothing for the description to clarify; baseline 4 applies. The description adds no parameter meaning, but none is needed.

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 leans on undefined jargon ("R/IV", "RVO", "independent evidence-verification primitive") and never states a concrete verb+resource an agent can act on. The name "control.check" and the phrase "evidence-verification" are not clearly reconciled, and nothing distinguishes it from siblings like claim.check, citation.verify, 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 when-to-use guidance, no prerequisites, and no reference to any alternative among the many overlapping verification siblings (claim.check, number.verify, transaction.verify, etc.). An agent has no basis for choosing this tool over them.

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