get_btc_multisig_utxos

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

Annotations already declare readOnlyHint, destructiveHint, etc. Description adds behavioral details: same gap-limit walk as get_btc_multisig_balance, each UTXO contains witnessScript and cosigner pubkeys, and 'no device touch'. No contradictions.

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?

Three sentences, front-loaded with purpose. Every sentence provides distinct value: purpose, behavior, usage context. No wasted words.

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?

No output schema, but description clarifies what each UTXO carries. Mentions relationship to other tools. Lacks pagination or limit details, but acceptable for a simple read-only tool.

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 covers 50% of params (only walletName described). Description adds context for walletName (links to prepare_btc_multisig_send) but offers no info on gapLimit despite referencing 'gap-limit walk'.

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?

Description clearly states it returns UTXO set for a registered multi-sig wallet. Distinguishes from sibling like get_btc_multisig_balance (balance) and prepare_btc_multisig_send (uses UTXOs) through explicit mention.

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?

Describes two use cases: internal use by prepare_btc_multisig_send and direct inspection. Provides clear context but lacks explicit when-not-to-use or alternative tools beyond the mentioned sibling.

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