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

Goes well beyond the annotations by disclosing the payment mechanic (free allowance keyed by caller, otherwise $0.01 USDC on Solana), the one-key-per-charge semantics, and the return shape ('signed verdict with the record's as-of time'). It also bounds expectations ('not a guarantee of future behaviour'). It does not explain why readOnlyHint is false (presumably the charge), which an agent might find mildly confusing, but there is no contradiction.

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?

Three tightly packed sentences with the core action front-loaded and pricing/payment details following. The em-dash parenthetical and clause stacking make it dense to parse, but no sentence is 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 does the work of naming the return ('signed verdict' plus 'as-of time'), and it flags the paid path so an agent isn't surprised. Remaining gaps are the unexplained liveness parameters and no indication of what the verdict looks like or how failures/refusals are reported.

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 schema already documents all five parameters, including that 'caller' keys the free allowance. The description reinforces caller/subject semantics and per-call scope but says nothing about the three optional liveness_* parameters, leaving that schema text to stand alone. Baseline 3 is appropriate.

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 and resource: 'Check one construct's standing record on the 402 Open Book', scoped to exactly one key/identity per call. An agent can distinguish it from attest/formula siblings in the reputation_* family, though the description never names those siblings to sharpen the boundary.

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 context is implied through the pricing model (free within the 100/day allowance, otherwise $0.01 USDC), which tells the agent cost trade-offs but not when to choose this over reputation_attest, reputation_formula, or commons_get_operator_reputation. The only real guidance is negative ('does not include identity verification'), with no named alternative tool to route to.

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