transfer-tokens

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

No annotations are provided, so the description carries the full burden. It only states a transfer occurs, which is obvious. It omits behavioral traits like requiring wallet data, password, or explicit confirmation (though the confirmAction parameter description notes this, the description itself does not). It does not mention side effects, reversibility, or network fees.

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 description is a single sentence (10 words) which is concise but arguably too terse. It earns its place but could include key context like requiring wallet setup without being verbose.

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?

Given the complexity (8 parameters, 4 required, no output schema), the description is incomplete. It doesn't describe return value, success/failure behavior, or prerequisites like having a wallet. Sibling tools like create-wallet suggest wallet must exist, but this is not mentioned.

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 baseline is 3. The description does not add any parameter meaning beyond what the schema already provides. It lists 'RBTC or ERC20 tokens' but doesn't explain how tokenAddress works relative to RBTC.

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 action ('Transfer'), the resource ('RBTC or ERC20 tokens'), and the context ('on Rootstock blockchain between wallets'). It distinguishes from sibling tools like check-balance or create-wallet, though it doesn't explicitly differentiate from attest-transfer.

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?

The description provides no guidance on when to use this tool versus alternatives. No when-not scenarios, prerequisites, or exclusions are mentioned. Sibling tools like attest-transfer or deploy-contract might have overlapping contexts but are not addressed.

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