solana_transfer

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 does disclose a key behavioral fact (private key from environment) and the source of funds. However, it omits important details like the transaction being irreversible, whether it returns a transaction hash, or how network/fees are handled.

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?

A single, well-structured sentence conveys all essential information without redundancy. It is front-loaded and every word contributes to the meaning.

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 simple two-parameter transfer tool, the description adequately covers the core flow: source, destination, and asset. It does not mention return values or confirmation behavior, but the absence of an output schema and the tool's simplicity reduce the impact of this omission.

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 input schema already provides complete descriptions for both parameters (100% coverage), so the description adds little beyond clarifying the sender. The description does not introduce additional nuance such as unit precision or gas considerations, but this is acceptable given the schema's clarity.

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), resource (SOL), source (keypair), and destination (another address). This distinguishes it from sibling tools like solana_execute_swap and transfer_native_token, making its purpose unambiguous.

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 clear context by specifying that the transfer is from the user's own keypair using the private key from the environment. However, it does not explicitly mention alternatives or exclusions, such as SPL token transfers or swaps, so it falls short of a 5.

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