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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new and important context: that it returns raw verification material and explicitly 'does not itself certify identity or future performance,' which warns the agent against treating the output as a verdict. That is a meaningful behavioral caveat beyond the annotations.

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 two sentences with no filler, and the disclaimer is placed last where it carries weight. However, the long comma-delimited inventory of cryptographic artifacts is dense and includes undefined jargon ('the current pulse', 'terms hash'), which slows comprehension more than it aids it.

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 zero parameters and no output schema, the description must carry the whole burden of explaining what comes back, and it does list the returned items. It still leaves gaps: how the returned material should be used to reach a verification conclusion, whether verification is scoped to a single current offer or to the provider generally, and whether multiple offers can be checked in one call.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly spends no words on inputs and instead explains outputs.

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 names the specific resource (verification material for the human provider and the signed offer) and enumerates exactly what that material covers: offer text SHA-256, wallet addresses, BIP-322/EIP-191/GPG signatures, DNS TXT record, GPG key locations, terms hash, and pulse. It is clearly distinct from payment/quote siblings like get_quote and get_receipt, though the opening phrase 'Evidence for checking...' is a noun phrase rather than a clean verb, leaving the actual action to the second sentence.

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?

Usage is implied: use this when you need to check the provider's humanity and the signature on an offer. There is no explicit when-to-use statement, no statement of prerequisites (e.g., whether an offer must exist first), and no comparison to the nearest alternative such as get_quote or get_status.

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