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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that the request is paid, which is a meaningful behavioral trait, and lists the data returned (status, classification, selector, gas, logs, RPC evidence). It implies a read-only retrieval, but does not discuss idempotency, rate limits, auth, or error behavior. The disclosure is partial, hence a mid-range score.

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 sentence that is front-loaded with the core action ('Retrieve a Base or Ethereum transaction and receipt in one paid request') and then enumerates the return attributes. It is efficient and contains no filler, though it is slightly dense with a long list of features. Overall it earns its place.

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 retrieval tool with two parameters, the description provides a solid overview of what is returned (deterministic status, classification, selector, gas cost, logs, raw RPC evidence). It notes the paid nature and the chain range. It does not cover failure/error cases or the exact output structure, but the core information an agent needs to decide whether this tool fits the task is present.

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 description coverage is low (only tx_hash has a description). The description compensates by explicitly naming the supported chains ('Base or Ethereum') and implying the tx_hash is the identifier for the transaction. It also explains that the tool returns a receipt, linking parameter purpose to the output context. This adds meaning beyond the raw schema, though tx_hash semantics could be more explicit.

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 and resource: 'Retrieve a Base or Ethereum transaction and receipt in one paid request.' It clearly differentiates the tool's scope from most sibling tools (which cover DNS, email, web content), though it doesn't explicitly call out a sibling alternative. The extra qualifiers (deterministic status, classification, method selector, gas cost, logs, raw RPC evidence) make the purpose precise.

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 alternatives. The description mentions 'paid request' but does not explain prerequisites, chain-specific considerations, or situations where another sibling tool (e.g., chain_contract_call) would be more appropriate. No exclusions or conditions are given.

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