wallet_transfer_sol

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

No annotations are provided, and the description fails to disclose key behavioral traits: it is a state-changing operation (sends SOL), requires a local wallet that must exist, and involves potential fees or errors. The description only says 'Send SOL', lacking details on consequences and prerequisites.

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, front-loaded sentence that conveys the core purpose efficiently. It earns its place but could be slightly expanded without losing conciseness. Very short but not wasteful.

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 tool has 5 parameters (2 required) and no output schema, the description is severely incomplete. It omits expected output (e.g., transaction hash), prerequisites, error behavior, and usage examples. The tool is part of a complex flow (x402), but the description provides only a hint.

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 description adds no information about parameters (walletPath, toAddress, lamports, sol, rpcUrl). Schema coverage is only 40%, and the tool description does not clarify the relationship between lamports and sol, or the meaning of walletPath. The description fails to compensate for schema gaps.

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 ('Send SOL'), source ('local wallet'), destination ('destination wallet'), and specifies its role in 'x402 paid key flow', distinguishing it from other wallet tools.

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 mentions the tool is 'used in x402 paid key flow', implying a specific use case but does not explicitly explain when to use it versus alternatives like wallet_get_balance or wallet_create_local. The context is present but not fully developed.

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