prepare_solana_nonce_init

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

Annotations indicate destructive and not readOnly. The description adds behavioral context: costs (0.00144 SOL + tx fee), rent reclaimability via close, and use of regular recent blockhash. This goes beyond the annotations without contradicting them.

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, well-structured paragraph with front-loaded purpose, alternative info, use cases, costs, and behavior. It is dense but clear; slight improvements could be made by breaking into bullets, but current is efficient.

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 has one parameter (fully documented in schema), no output schema, and annotations provide basic hints, the description covers purpose, alternatives, when to use, cost, reclaimability, refusal condition, and technical blockhash detail. It is comprehensive for this tool's complexity.

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 schema's own description for 'wallet' is already detailed (derivation, no backup needed). The tool description reiterates the derivation string but adds no significant new meaning beyond the 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 identifies the tool as the explicit one-time setup of a per-wallet durable-nonce account at a specific deterministic PDA. It distinguishes from sibling tools like prepare_solana_native_send by noting that most users do not need to call this directly because those tools auto-bundle the setup.

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 explicitly states when to use this tool (standalone before Jupiter swap or MarginFi action, or to re-init after close) and when not to (most users should rely on auto-bundling). It also mentions that it refuses if a nonce account already exists.

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