transfer_token

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

With no annotations, the description carries the full behavioral burden but only says the transfer is possible. It never states that the operation is an irreversible on-chain mutation, that it requires an unlocked wallet/signing key, that a network fee is deducted, or what the caller gets back on success.

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 action and the token-identifier convention are front-loaded in two short lines with zero filler. The trailing 'Tip' about earning_opportunities is tangential but brief enough not to bloat the 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 value-moving mutation with no annotations and no output schema, the description should cover prerequisites and outcomes. Missing are auth/signing requirements, irreversibility, fee behavior, and whether a transaction ID is returned, leaving the agent to guess at the critical context for a fund transfer.

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%, so all five parameters (fee, memo, token, amount, recipient) are already documented in the schema, including fee presets and the 34-byte memo limit. The description adds only the concrete symbol examples (sBTC, USDCx, ALEX, DIKO) on top of the schema's 'USDCx' example, so the 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 any SIP-010 token to a recipient address'), which cleanly separates it from transfer_nft and transfer_rune. It does not address why one would use it instead of the sibling sbtc_transfer, even though sBTC is explicitly listed as a supported symbol, leaving that overlap unresolved.

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 standard 'transfer tokens' framing; there are no stated preconditions (wallet unlocked, sufficient balance) and no exclusions. The one explicit pointer, 'call earning_opportunities', is a cross-sell nudge rather than guidance about when to pick this tool over its near-neighbors.

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