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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the exact response payload when confirmed, and the important fact that a pending or unknown transaction yields a normal {confirmed:false} response rather than an error — that is the detail an agent most needs to avoid misreading a negative result.

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 tight body sentences lead with the action and the return shape before the edge case; the doc link and REST operation line are short and additive rather than repetitive. Slight waste in restating the endpoint after the docs link.

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 lookup with an output schema and full annotations, this covers what an agent needs: what it returns, and how unconfirmed transactions appear. The only gap is error/permission behavior for a malformed or non-existent txid, which the description folds into the generic 'not in the chain' case.

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 reported as 0% because the single property is a $ref, and the description says nothing about txid at all. In practice the $defs entry supplies a description, a 64-hex pattern, and three examples, so the parameter is still documented — but the credit belongs to the schema, not the description.

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 states a specific verb and resource ('Retrieve the confirmation status of a transaction') and enumerates exactly what is returned (confirmed flag, block height, hash, timestamp), which implicitly separates it from get_tx / get_tx_hex / get_tx_merkle_proof. It never names a sibling tool explicitly, so an agent must infer the boundary rather than read it.

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 when-to-use guidance and no mention of alternatives in a sibling list that contains at least four other transaction-level tools (get_tx, get_tx_hex, get_tx_merkle_proof, get_transaction_times). The 'pending or unknown returns {confirmed:false}' line describes output behavior, not selection criteria, so the agent is left to infer routing on its own.

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