prepare_jito_stake

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

The description goes beyond annotations by detailing the underlying DepositSol instruction, automatic ATA creation with 0.002 SOL rent, need for blind-signing, and use of durable nonce. It also explains why an ephemeral keypair is avoided.

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 front-loaded with the main action, then provides essential technical details and warnings in a structured manner. Every sentence adds value without redundancy.

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?

The description covers input requirements, behavior, and warnings thoroughly. It mentions that the tool builds an unsigned transaction and is compatible with preview_solana_send. No output schema is needed as return value is implied.

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%, and the description adds valuable context: wallet must have nonce init and sufficient SOL, amountSol is human-readable with 9-decimal precision and rounds down to 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 builds an unsigned Jito stake-pool deposit transaction for staking SOL to receive jitoSOL. It distinguishes from siblings like Lido and Marinade staking by specifying Jito-specific details and Ledger compatibility.

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 explains when to use this tool (Jito staking) and specifies prerequisites (durable nonce, prepared nonce init). It also warns against using high-level helper for Ledger users and mentions that unstaking is not yet available.

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