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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: unconfirmed UTXOs are returned, and mempool-spent outputs are filtered out. It does not cover ordering, volume, or size of results, but the output schema carries the return shape.

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 with the inclusion/exclusion rule front-loaded, followed by a docs link and the REST operation. The REST line is mild overhead but gives useful traceability to the upstream endpoint; nothing is padded.

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?

A single-parameter read tool with annotated safety hints and an output schema. The description supplies the semantics annotations cannot express (unconfirmed inclusion, mempool-spend exclusion), and return values need not be restated. Nothing an agent needs in order to call it correctly is missing.

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% at the property level, though the referenced Address definition does carry 'Bitcoin address, or the hex public key of a P2PK output' plus three examples. The description adds only the REST path template `{address}`, which confirms a single required address argument but contributes no format or validation detail beyond the schema.

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 ('Get unspent transaction outputs (UTXOs) for an address') and goes on to define its exact scope: unconfirmed outputs are included, outputs spent by mempool transactions are excluded. That inclusion/exclusion contract is what separates it from siblings like get_address_txs or get_address without the agent needing to open a schema.

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 rather than stated. There is no 'use this when... use get_address_txs instead when...' guidance, and no mention of prerequisites such as address validation via validate_address. An agent can infer the use case from the resource name, but the definition does not route it among the 70+ siblings.

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