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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the ordering guarantee (output-index order), which is a genuine but minor behavioral detail; it says nothing about cost, rate limits, or behavior for spent/unspent outputs.

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?

Very short and front-loaded: the ordering semantics come first, followed by a docs link and the REST operation. Nothing is padded, though the doc-link and REST-path lines add little for an agent that already has the schema.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. The remaining material gap is disambiguation from get_tx_outspend and any hint about the txid input, which the description omits.

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 0% per the context signals, and the description never mentions the single `txid` parameter, its required status, or its format. The only parameter meaning lives in the schema's $defs (`Txid`), so the description does not compensate for the coverage gap.

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 phrase "Spend statuses in output-index order" plus the REST path `GET /api/tx/{txid}/outspends` implies it returns the spend status of every output of a transaction, but the verb and object are only inferable from the URL. It never states explicitly that this is the plural/all-outputs variant, so it is not cleanly distinguishable from the sibling get_tx_outspend.

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?

No when-to-use guidance at all. The most important routing decision — all outputs (this tool) vs. a single output (get_tx_outspend) — is left entirely to the agent, even though that sibling is present in the tool list.

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