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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint. Beyond that, the description usefully discloses what the call reports (live status, jury config, facilitator selection, receipt count, price) — return-value context that matters since no output schema exists. It does not state whether the call requires auth or whether price retrieval is free.

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?

A single front-loaded sentence that leads with the primary check ('whether ClaimGate is live') and then enumerates secondary facts. Dense but every clause names a distinct config surface, so there is no filler.

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, the description carries the burden of describing return content, and it largely does by listing the five facts reported. A read-only, idempotent, zero-param tool needs little more, though a note that it requires no auth and is free to call would close the remaining gap.

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 the baseline is 4; there is no parameter semantics an agent could get wrong. The description correctly implies no input 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 gives a concrete verb ('Check') plus an enumerated set of system facts (ClaimGate liveness, Jev jury configuration, x402 facilitator, receipt count, paid-check price), which makes clear this is a diagnostic/status tool. It is implicitly distinguishable from siblings like fact_check_claim and fact_check_receipt, though it never names them.

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 only implied: an agent can infer this is a pre-flight/config check to run before invoking paid checks, but the description never says when to use it, when not to, or how it relates to the four sibling tools. No exclusions or alternatives are stated.

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