Generate Wallet

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

The description adds value beyond the annotations by clarifying that the tool provides instructions for local generation rather than executing the generation itself. This aligns with the readOnlyHint=true annotation, and the description explains the tool's actual behavior (delivering code/instructions, not performing actions on the server).

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, using two sentences to convey the purpose, workflow, and next steps. Every sentence adds value with no wasted words.

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 no parameters, no output schema, and annotations that already cover safety, the description provides complete context: it explains what the tool does (provides instructions), where to generate (locally), and what to do after (fund and stake). No additional information is needed for proper use.

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?

There are zero parameters, so the schema already provides full coverage. The description does not need to explain parameters, and the baseline score of 4 is appropriate.

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 provides 'instructions and code to generate a Solana wallet locally,' specifying the verb 'get instructions/code' and resource 'wallet generation instructions.' It distinguishes itself from sibling tools by indicating it does not actually generate the wallet on the server but guides local generation.

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 gives explicit sequential guidance: use this tool to get instructions, then fund the wallet, then use the 'stake' tool. It implies when to use this tool (when you need to create a new wallet) and hints at next steps, but does not explicitly mention scenarios where this tool should not be used or alternatives.

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