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

Annotations already indicate readOnly and openWorld hints, so the description carries a lower burden. It adds return-content details (from, to, value, input data, status), but the inclusion of 'status' is inaccurate for a standard Ethereum transaction object, which undermines trust in the behavioral disclosure.

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 two sentences, front-loaded with the action and network, and contains no filler. Every word contributes to explaining the tool's purpose.

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 one-parameter read-only tool with a full schema and annotation safety profile, the description provides a reasonable overview. It lacks explicit error behavior (e.g., null if not found) and contains a possible inaccuracy ('status'), so it is not fully complete.

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 schema fully covers the single 'hash' parameter with pattern and description, so the description adds no additional parameter semantics beyond what is already structured. Per the baseline for high schema coverage, a score of 3 is appropriate.

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 clearly states a specific verb ('Get'), resource ('transaction details'), and scope ('Ethereum mainnet'), distinguishing it from sibling tools like btc_get_transaction and eth_get_transaction_receipt. The phrase 'by hash' precisely identifies the lookup method.

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 use for fetching transaction data on Ethereum mainnet but does not explicitly mention alternatives or exclusions, such as when to use eth_get_transaction_receipt instead. The network scope is stated, but no 'when not to use' guidance is provided despite many sibling tools.

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