Initialize ORDnet Wallet

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

Annotations already declare idempotentHint=true and non-destructive, and the description adds valuable security context: 'WIF is held in memory only, not persisted.' It also discloses fee details and that this is non-production (via the init_env reference). No contradiction with annotations.

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?

Well-structured with sections (intro, use cases, security, args, returns, example). It is somewhat verbose with fee details, but each section serves a purpose and the key information is front-loaded. Not wasteful overall.

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 tool is relatively simple with one parameter and no output schema. The description covers return value, example, security, and usage context. It lacks error-handling details, but that is not essential given the schema and annotations. Complete enough for a single-purpose init tool.

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% with wif described in the schema (pattern, minLength, maxLength). The description repeats the format and adds an example, but does not significantly augment the schema's meaning. Baseline 3 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 'Initialize wallet from WIF private key for blockchain operations', using a specific verb and resource. It differentiates from siblings by mentioning 'Use ordnet_wallet_init_env for production' and positioning itself as the initial step before inscription creation.

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 'This is the first step before creating inscriptions' and lists concrete use cases (creating/signing, paying fees, receiving change). It also provides an explicit alternative: 'Use ordnet_wallet_init_env for production', giving clear when-to-use guidance.

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