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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds genuinely new behavioral context beyond that: the per-call cost (0.005 USDC on eip155:84532), which reconciles the non-read-only flag, and the requirement to persist the private idempotencyKey for retries. It does not, however, describe the return payload or latency/rate behavior.

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 short sentences, front-loaded with purpose and then cost and retry mechanics; nothing is bloated. The idempotency sentence is somewhat redundant with the schema description, which keeps it from a 5.

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 and two parameters, the description should say more about what comes back (the raw RLP-encoded transaction hex) and what params represents. It covers purpose, cost, and idempotency adequately for invocation, but leaves the return value and the hash parameter unexplained.

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 50%: the idempotencyKey field is already fully documented in the schema, and the description's retry note only reinforces it. The params array (a single 0x-prefixed 64-hex transaction hash) is documented in neither the schema nor the description, so the description does not compensate for that gap.

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 verb ('Read') and the resource (eth_getRawTransactionByHash) plus the chain (eip155:1), so the operation is identifiable. However, it largely restates the self-descriptive method name and offers no differentiation from close siblings such as ethereum_eth_getRawTransactionByBlockHashAndIndex or ethereum_eth_getTransactionByHash.

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 on when to use this tool versus the many sibling getters (e.g., getTransactionByHash returns the decoded transaction, this returns the raw encoded one). The only operational note is preserving the idempotencyKey, which is retry mechanics rather than tool-selection guidance.

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