transfer_sol

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

No annotations are provided, so the description is responsible for behavioral disclosure. It states 'transfer' (implying mutation) but does not mention side effects (e.g., fees, nonce reuse), the 'simulateOnly' parameter's existence, or what happens on success/failure. This is a significant gap for a mutation tool.

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 extremely concise, consisting of two clear sentences. The first sentence front-loads the core purpose, and the second provides a critical prerequisite. No unnecessary words or repetition.

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's complexity (mutation with 4 parameters, no output schema), the description is insufficient. It does not explain return values, error conditions, transaction fees, or network prerequisites. Context signals show no output schema, so the description should provide behavioral context, which it lacks.

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?

All four parameters are described in the input schema (100% coverage). The description adds 'Requires sender private key (base58)', which reiterates the schema's description of 'fromPrivateKey'. No additional meaning is added beyond the schema, so the baseline score of 3 applies.

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 ('SOL'), and the direction ('from one wallet to another'). It distinguishes this tool from siblings like 'transfer_token' by specifying the asset type. The requirement of a private key is also mentioned, adding specificity.

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 does not explicitly guide when to use this tool over alternatives. It mentions the requirement of a private key, which is implicit for any transfer, but does not differentiate from other transfer tools like 'transfer_token' or provide context for optimal use.

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