prepare_native_stake_delegate

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

Discloses key behavioral details beyond annotations: deterministic address derivation via createAccountWithSeed, rent-exempt seed amount (~0.00228 SOL), authority roles (wallet for both), refusal condition. Annotations indicate destructiveHint=true and idempotentHint=true, which align with creating a deterministic account. No contradiction.

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 dense paragraph covering all relevant details. It is front-loaded with the main action. Could be slightly improved with bullet points for readability, but overall efficient and free of fluff.

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 (Solana stake delegation with deterministic address, nonce, rent, ledger signing) and no output schema, the description covers prerequisites, behavior, refusal condition, and security notes. It is fully sufficient for an AI agent to understand and invoke correctly.

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 three parameters have schema descriptions with 100% coverage, but the description adds value by explaining the derivation (wallet+validator) for the address, clarifying amountSol is human-readable and actual lamports include rent-exempt, and warning about tx fee. This goes beyond schema.

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 it builds an unsigned native-stake-program tx to create a stake account at a deterministic address and delegate it to a validator. It distinguishes from sibling tools like prepare_native_stake_deactivate and prepare_native_stake_withdraw by noting it refuses if a stake account already exists, implying the user should use those instead. Also directs to call list_solana_validators first.

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?

Provides explicit prerequisites: durable nonce required, enough SOL for amount plus rent-exempt fee. Tells when not to use: if stake account already exists (use deactivate/withdraw). Mentions blind-sign on Ledger and suggests using list_solana_validators to pick a validator.

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