btc_sweep

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

Discloses key behavioral traits: fee deducted from inputs and resulting balance of 0 sats. With no annotations, this is helpful but could further mention irreversibility or the need for unlocked wallet.

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 sentences with no wasted words. The purpose is front-loaded, and every sentence adds value. Ideal conciseness for a tool description.

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 the core operation well, but lacks mention of return value (e.g., transaction ID) or error conditions. Since no output schema exists, the description could be more complete about what the agent can expect.

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 coverage is 100%, and the description adds context to fee_rate by noting it's deducted from inputs. This goes beyond the schema's standalone description, enhancing parameter understanding.

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 verb 'sweep' and the resource 'entire Bitcoin balance to one address'. It distinguishes from siblings like btc_send by specifying 'entire balance' and providing common user phrases that trigger this tool.

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?

Explicitly lists user commands that should trigger this tool ('send all', 'sweep', 'drain', 'empty wallet', 'move everything'), providing clear when-to-use guidance. It also implies when not to use (for partial sends) by contrasting with btc_send.

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