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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety is covered, but with no output schema the description must disclose what comes back — and it does, itemizing status, gas/fee in both ETH and USD, decoded ERC-20 transfers and Uniswap v2/v3/v4 swaps. It adds no note on latency, chain coverage limits, or error behavior for unconfirmed hashes, keeping it short of 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?

Two sentences, no filler: the trigger clause is front-loaded and the return-field enumeration is packed into a single dense sentence. Every element earns its place.

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 present, the description appropriately carries the return-value burden by listing fields. Minor gap: it does not explain the quote mode, and ambiguous hashes (wrong chain vs. unknown) are unaddressed.

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 coverage is 100%, so both the hash format and the quote flag are already documented in the schema, establishing a baseline of 3. The description adds nothing about the quote parameter (a price-check-without-execution mode), which is a non-obvious flag worth calling out.

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 (understand what a transaction did) and resource (Robinhood Chain transaction), and enumerates exactly what it returns: status, addresses, method, gas/fee, decoded ERC-20 transfers and Uniswap swaps. This is clearly distinguishable from token- or wallet-scoped siblings, though it never names them explicitly.

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?

'Use this when you need to understand what a Robinhood Chain transaction did' gives a clear trigger condition that maps to the transaction-inspection use case. It offers no when-not guidance and does not point to robinhood_rpc or robinhood_token as alternatives for related needs, so it stops short of full routing guidance.

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