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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds output-content context but does not disclose additional behavioral traits like whether only certain transaction types are supported or how unknown hashes are handled. No contradiction with annotations.

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 a single, front-loaded sentence with no filler. Every clause adds specific value: the chain, the plain-words output, and the concrete content of the explanation.

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-hash, read-only tool with strong annotations, the description covers purpose and output content well. It would be slightly more complete with a note about supported transaction types or behavior for unrecognized hashes, but those are minor gaps.

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 input schema fully documents the single parameter, hash, with a regex pattern and a clear description. With 100% schema description coverage, the tool description does not need to repeat parameter details, and the baseline of 3 applies.

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 exactly what the tool produces: a plain-language explanation of a Robinhood Chain transaction, including who paid what, what they got, and the pool or curve involved. This clearly distinguishes it from siblings like simulate_transaction, which is for speculative future transactions, and wallet_history, which lists transactions.

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?

The description implies the tool is for understanding what an existing transaction hash did, but it offers no explicit when-to-use or when-not-to-use guidance. It never mentions alternatives such as simulate_transaction or notes that this is not for simulating or listing historical activity.

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