prepare_solana_nonce_init

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

Adds significant context beyond annotations: explains creation cost (~0.00144 SOL rent-exempt + tx fee), rent reclaimability via close, why a regular blockhash is used (no nonce yet), and deterministic nature. No contradiction with annotations (destructiveHint=true matches creation of an account).

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?

Single paragraph is dense but front-loads key info. Could be slightly more structured (e.g., bullet points for cost/refusal), but no fluff. Good conciseness.

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 complexity of nonce setup, the description covers purpose, usage scenarios, cost, reclaimability, deterministic address, and constraints (refuses if exists, blockhash choice). No output schema, but return value is implied (transaction). Complete for agent decision-making.

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?

Only one parameter 'wallet'. Schema covers pattern and basic description; description adds value by explaining deterministic PDA derivation and that no separate keypair is needed. Schema coverage is 100%, so baseline is 3; extra context justifies a 4.

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 sets up a durable-nonce account, specifies the deterministic PDA derivation, distinguishes from siblings by noting auto-bundling in other tools, and lists specific use cases (standalone before Jupiter/MarginFi, re-init after close).

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?

Explicitly says when to use (standalone setup, re-init) and when not to (most users should rely on auto-bundling). Provides cost, reclaimability, and a condition that it refuses if nonce already exists.

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