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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added details about the status enumeration and returned payload (block, gas, explorer and The Desk links) are genuine extra context. It stops short of describing behavior for an unknown or malformed tx_hash, which keeps it from a 5.

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?

One compact sentence with zero filler that leads with the core outcome and then lists the returned fields. It reads as a noun fragment rather than a verb-led statement, a minor structural weakness.

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?

For a simple one-parameter read tool with no output schema, the description covers what the call resolves to and what comes back, which is most of what an agent needs. The only real gap is error behavior for invalid or unrecognized hashes.

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 0% and the description never references the single tx_hash parameter or its expected 0x-prefixed 64-hex format. The regex pattern in the schema partially compensates, but the description adds no semantic meaning of its own.

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 states a specific resource (a Robinhood Chain transaction) and enumerates the exact outcome it reports (pending, confirmed, failed) plus the data returned (block, gas, explorer links). It is clearly distinguishable from every sibling, none of which deals with transaction status, though it lacks an explicit verb like 'retrieve'.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent can infer it is for checking a known tx_hash, but the description never says so or when another tool (e.g. scan_contract) would be more appropriate.

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