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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuine value beyond them: it discloses the 'not found' outcome, the fields returned (block number, confirmations, from, to, value, token transfers, explorer link), and the dependency on what the explorer reports. The stray 'Example QIE ID: yourname.qie' is unexplained and slightly muddies an otherwise precise behavioral picture.

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 lead sentence is well front-loaded and information-dense, but the description carries two pieces of filler: an unexplained 'Example QIE ID: yourname.qie' that is irrelevant to a transaction-hash lookup and risks confusing an agent, and a boilerplate financial-advice disclaimer. Both consume space without helping the call.

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 steps in to describe the return payload and the possible 'not found' state, which is the main completeness risk for an open-world lookup. It also pins the two supported networks. Only the unexplained QIE ID example leaves a loose end an agent could misread.

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 100%, so both txHash and network are already fully documented, including the hash format and the chain-ID mapping. The description's mention of chain 1990/1983 merely restates the network field's schema text and adds no new semantics. Baseline 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?

States a specific verb and resource ('Read whether a transaction is pending, successful, failed, or not found') and enumerates the possible outcomes, which is exactly the mental model an agent needs. Scoping to QIE mainnet/testnet and the note that it does not submit transactions cleanly separates it from write-path or balance/name siblings.

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 establishes clear context (look up a tx by hash on a pinned network) and adds an explicit boundary: 'This does not submit a transaction.' It stops short of naming alternatives (e.g., use qie_get_balances for holdings, qie_resolve_name for addresses), so routing is implied rather than spelled out.

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