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

readOnlyHint=true already establishes the safe-read profile, and the description adds that it returns status, fee, timestamp, entities, balance changes and manifest. However, it does not mention behavior for non-existent or uncommitted hashes, nor any auth/rate considerations, so it only partially goes beyond the annotation.

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?

A single front-loaded sentence identifying the resource and key, followed by a compact colon list of returned data. No filler or redundancy.

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, listing the returned fields (status, fee, timestamp, entities, balance changes, manifest) usefully fills the gap, and the parameters are fully covered by the schema. Only the absence of error/edge-case behavior keeps it from a 5.

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%, with both network and intentHash fully documented in the schema. The description restates the txid_… format but adds no new syntax or constraint beyond the schema, so the baseline 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?

States a specific verb (Fetches), resource (committed transaction), and key (intent hash/txid). The word 'committed' implicitly distinguishes it from preview_transaction and the recent/address transaction list siblings, though no sibling is named explicitly.

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 implied by 'committed transaction by its intent hash', which signals you need a known txid rather than a filter, but there is no explicit when-to-use/when-not guidance or named alternative (e.g., get_recent_transactions, preview_transaction).

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