spl-token_transferSol

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

The description mentions SystemProgram.transfer but does not detail side effects (deducting SOL), prerequisites (sufficient balance), or other behavioral traits. With no annotations, the description carries full burden and could be more transparent.

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 with no wasted words. It efficiently conveys the core purpose.

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 transfer tool with 4 parameters and no output schema, the description is adequate but lacks details on return value (e.g., transaction signature) or error conditions. It could be more complete.

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 the baseline is 3. The description adds no additional meaning beyond the schema, which already describes parameters like amount in lamports.

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 tool transfers native SOL between wallets via SystemProgram.transfer, distinguishing it from the sibling tool spl-token_transfer which handles SPL tokens.

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?

While no explicit when-to-use or when-not-to-use guidance is given, the name and description imply it is for native SOL only. The sibling context shows a separate spl-token_transfer for tokens, making the usage context clear.

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