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

Annotations declare openWorldHint=false, but the description says it verifies against real external world state and runs HTTP status/page-text/JSON read-back checks. That is a direct contradiction. The receipt/confidence/cost details are useful, but the contradiction forces a 1 under the annotation-contradiction rule.

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?

The description is four sentences, front-loaded with purpose, then mechanics, usage, and cost. Every sentence earns its place with no redundancy.

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?

An output schema exists, so return values need not be explained in detail. The description supplies purpose, trigger, mechanics, and cost; it omits auth/payment-key details, but the schema covers payment_signature.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds context about check types (HTTP status, page text, JSON fields) and cost, but it does not add per-parameter meaning beyond what the schema already provides.

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?

States a specific verb 'Verify' and object 'agent's completion claim against real external world state.' It distinguishes itself from siblings such as vc_agent_reputation and vc_agent_state_guard by focusing on independent read-back proof of a completion claim.

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?

Explicitly says to use it after an agent says it posted, deployed, paid, emailed, or changed a record, giving a clear trigger. It does not name alternatives or when-not-to-use cases, so it falls short of a full 5.

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