unregister_btc_multisig_wallet

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

Beyond annotations (destructiveHint, idempotentHint), the description explains that the Ledger device retains the policy HMAC, the tool only forgets local entry, and idempotency with `removed: false` response. 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?

Well-structured with clear front-loading: purpose first, then behavioral context, then usage guidance. Every sentence adds value, though slightly verbose; could be slightly tighter.

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?

Covers purpose, Ledger behavior, usage scenarios, and idempotency. Lacks explicit output format details, but description hints at return value. Adequate for a simple tool with no output schema.

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?

The input schema already provides a detailed description of walletName, covering idempotency and HMAC retention. The main description does not add new parameter-specific information beyond what's in 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?

The description clearly states the tool's purpose: 'Drop a registered multi-sig wallet from the local cache.' It uses specific verb (drop) and resource (BTC multisig wallet), distinguishing it from siblings like register_btc_multisig_wallet.

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?

Explicit guidance: 'call it before re-registering with different cosigners under the same name, or to clean up wallets you no longer use.' Also explains the device's HMAC retention, setting expectations for re-registration behavior.

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