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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description usefully adds the semantic edge case that an output not held by any known transaction is reported as unspent. The docs link and REST operation mapping add further traceability, though nothing is said about mempool-vs-confirmed behavior or failure cases.

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 sentences lead with the core answer, followed by the edge-case rule, doc reference, and REST endpoint mapping. No filler; every element is front-loaded and 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?

With an output schema present and annotations covering the read-only profile, the description needn't explain return values, and it does supply the crucial 'unspent' interpretation rule. The only real gap is the absent differentiation from the plural get_tx_outspends sibling.

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 50%, and the $defs already document both txid (hash format) and vout (output index, with the coinbase 4294967295 note). The description adds no parameter meaning beyond that, so the baseline of 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+resource: determines whether a given transaction output has been spent and returns the spending transaction details. The singular 'outspend' implicitly differs from the sibling get_tx_outspends (plural), but the description never makes that contrast explicit.

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 the plural get_tx_outspends sibling, nor on prerequisites (e.g., needing a confirmed txid/vout). The only contextual sentence — 'An output no known transaction holds is unspent' — explains result semantics rather than usage routing.

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