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

Annotations already declare readOnly, idempotent, and closed-world, so the bar is lower. The description adds the useful fact that the response includes every transaction in order with decoded swaps/transfers/liquidity changes, which hints at a heavy payload, but it never states this explicitly (no size/cost/pagination warning) or what happens at the chain tip when 'latest' is requested.

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?

Front-loaded with the resource and scope, which is good, but the second half is one long comma-chained enumeration of return fields that is hard to scan and partially duplicates what a reader can infer from the transaction concept. A short structured field list would earn the space better.

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, the description does legitimate work by enumerating return contents (hash, time, gas, tips, HYPE burnt, per-tx sender/recipient/status/decoded swaps). However it omits any routing context relative to ~80 sibling tools and gives no behavioral caveats, so an agent can form a call but not judge when it is the right call.

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 the schema documents layer, number, and network including the testnet-USD-null caveat. The description restates 'a number, or latest' and the layer names but adds no format, range, or default guidance beyond what the schema already provides.

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+resource ('One HyperEVM or Elysium block (a number, or latest)') and names the two supported chains, so the agent knows exactly what entity is returned. It never distinguishes itself from adjacent tools like get_transaction, elysium_rpc, or get_gas, which is the one thing keeping it below 5.

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 signal at all: nothing tells the agent to prefer this over get_transaction for a single tx, or over elysium_rpc for raw chain access, or when a block-by-block read is the wrong approach (e.g. for historic aggregations). Usage is only implied by the resource name.

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