Spl-token Transfer Sol

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

Description indicates a write operation but does not disclose behavioral traits beyond annotations. No mention of balance changes, fees, or authorization requirements. Annotations already provide safety profile, so additional context is limited.

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?

Description is verbose with generic SAP context that does not aid the agent. The first sentence is clear, but subsequent sentences are irrelevant and not concise.

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 native SOL transfer, the description is adequate but lacks details on system program usage and return value. Output schema exists, so return value explanation is not required, but additional context could improve completeness.

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?

Input schema covers all parameters with descriptions (100% coverage). Description adds no meaning beyond schema, meeting baseline.

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 states it transfers native SOL between wallets via SystemProgram.transfer, which is specific. However, it includes irrelevant text about SPL token operations, diluting clarity.

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?

No explicit guidance on when to use this tool vs alternatives. The description mentions SPL token operations, which is misleading for a SOL transfer tool. Sibling tools like spl-token_transfer exist but are not differentiated.

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