sbtc_transfer

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

With no annotations, the description carries the full behavioral burden for a value-moving mutation, yet it says nothing about irreversibility, confirmation, failure modes, or whether fees are deducted from the amount. The only added behavior detail is the decimals convention, which is really a parameter issue; the sponsored/fee mechanics live in the schema, not here.

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?

The core purpose is front-loaded in one line and the decimals/satoshi note is genuinely useful for avoiding unit errors. The trailing tip about `earning_opportunities` is promotional and arguably does not earn its place in a transfer tool's definition.

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?

For a 5-param mutation with 100% schema coverage and no output schema or annotations, the description covers purpose and unit semantics adequately. What is missing is risk context — that the transfer is irreversible and what happens if the fee is omitted — but the schema handles the rest.

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 100%, so the parameters (fee presets, memo, sponsored env requirement, amount) are already fully documented. The description's decimals explanation and 0.001 sBTC example restate what the `amount` schema entry already says, adding no net value; baseline 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 and resource ('Transfer sBTC tokens') with the target (recipient address), which is clear enough to distinguish it from transfer_stx or transfer_btc by asset name. However, it never explicitly contrasts itself with the many sibling transfer tools, so an agent must infer differentiation from the name alone.

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 only implied by the verb 'transfer'; there is no explicit statement of when to use this versus transfer_token, transfer_stx, or sbtc_initiate_withdrawal, nor any prerequisite notes. The closing tip points at `earning_opportunities`, but that is a cross-sell rather than guidance on tool selection.

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