create_wallet

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

No annotations are provided, so the description carries the burden. It says 'Create or import' which implies mutation, but it doesn't disclose side effects like whether it stores the wallet, how private keys are handled, or if it returns the keypair. It adds the 'implicit account info' detail, but misses specifics like network selection behavior or privacy implications.

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 sentence, concise, and to the point. No fluff. Perfectly sized for the purpose.

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 4 parameters, no output schema, and no annotations, the description is somewhat incomplete. It doesn't explain what 'implicit account info' returns, how network affects the wallet, or the implications of include_private_key. However, the tool is relatively simple, and the description covers the core action. It's adequate but leaves gaps.

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 50%, with descriptions on account_id and private_key, but network and include_private_key lack descriptions. The description mentions 'Create or import' which covers the private_key parameter, but doesn't clarify network or include_private_key. With 50% coverage, the description should compensate more, but it adds minimal semantic value 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 states the tool creates or imports a NEAR wallet (keypair), which is specific and distinguishes it from sibling tools like check_balance and sign_transaction. However, it doesn't mention the 'include_private_key' behavior or 'implicit account info' details, but the core purpose is clear.

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 implies when to use: when you need to create or import a wallet. But it doesn't provide explicit guidance on when not to use it or alternatives; relying on sibling names, it's clear this is for wallet creation, not balance checks or signing. Adequate but not explicit.

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