create_wallet

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

Discloses that the tool returns the private key and is non-custodial, but does not mention authentication needs, rate limits, or potential side effects like overwriting an existing wallet.

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?

Extremely concise single sentence that front-loads the action and includes essential return information 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?

The description covers main behavior and return values, which compensates for missing output schema. Lacks details on error conditions or warnings about handling sensitive private key data.

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%, but description adds beyond schema by explaining that private_key is for restore and that the tool returns address and private key, providing context not in 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 states 'Create or restore a non-custodial wallet' with a specific verb and resource, and distinguishes from sibling tools like get_balance and send by focusing on wallet lifecycle.

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?

Implied usage (create vs restore) but lacks explicit guidance on when to choose this tool over alternatives or prerequisites like requiring caller to store key.

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