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

The readOnlyHint annotation already signals a read-only operation, lowering the bar. The description adds a small amount of behavioral context by mentioning 'the chain's record' and 'attestation check,' but it is still too vague to convey meaningful details such as what is verified, what is returned, or whether external dependencies exist. No contradiction with annotations is present.

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 short, but brevity here is under-specification rather than effective concision. The single sentence does not earn its place because it fails to define the operation clearly.

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?

Although the input schema is small, the description omits essential context: what the result looks like, what the hash means, and how this tool relates to similar siblings. The combination of vague prose and an undocumented parameter leaves the tool under-specified for an agent.

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?

There is one required parameter, 'hash', with zero schema description coverage. The description never explains what the hash refers to — transaction hash, attestation hash, or record ID — so the agent cannot confidently infer how to populate the parameter.

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 gestures at a purpose — settlement, the chain's record, and an attestation check — but uses no verb and never states a concrete action such as fetch, validate, or return. It is vaguely informative but does not clearly distinguish this tool from siblings like rh777_receipts or rh777_summary.

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 guidance about when to use this tool versus alternatives. The required 'hash' parameter implies a lookup-by-hash operation, but the description does not state conditions, exclusions, or how this differs from the other rh777 and metamuse tools.

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