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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), yet the description adds real behavioral context: logs are capped at 100, event string values are untrusted, log decoding depends on a verified ABI or standard ERC-20/721 matching, and a pending transaction yields no receipt. The untrusted-data warning and the log cap are exactly the kind of operational caveats an agent needs before consuming the output.

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, front-loaded with the resource and its main fields, then the log details and the pending-transaction caveat. Dense but not padded — the enumeration earns its place because there is no output schema. Slightly list-like, but nothing is redundant.

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 no nested params, the description carries the return-value burden and does it well: field-by-field contents, units for the fee/gas price, the log cap, decoding rules, and the pending-transaction edge case. An agent knows what it will receive and when it will get nothing.

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?

There is a single required parameter (hash) and schema description coverage is 100%, with the schema stating '0x-prefixed 32 bytes'. The description never mentions the hash argument or adds validation/format guidance beyond that, so 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 names a specific verb+resource (retrieve the receipt of a mined transaction) and enumerates exactly what that receipt contains: status, gas used, effective gas price, fee paid, created-contract address, and event logs. The closing line 'A transaction that is not mined yet has no receipt' cleanly separates it from get_transaction in the sibling list. An agent can pick this tool over get_transaction or get_logs without opening any schema.

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?

Usage is only implied: the receipt exists for mined transactions and is absent otherwise, which tells the agent the precondition but not how to respond. No sibling is named as an alternative or a complement (e.g. get_transaction for pending txs, get_logs for log-only queries). Adequate context, but the routing decision is left to inference.

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