Wallet List

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly indicates a non-mutating read operation, identifies the storage location, states returned fields, and explicitly warns that private keys and seed phrases are never exposed. This is strong behavioral context for a simple listing tool.

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 short and well-structured, with the core action front-loaded and the security note placed at the end. The first two sentences are slightly redundant ('List all wallets' vs 'Returns information about all wallets'), but overall it is tight and scannable.

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?

For a zero-parameter list tool, the description is complete: it states what is listed, where from, what fields are returned, and what sensitive data is not included. An output schema is present, so return-value details do not need to be repeated in the description.

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?

The tool has zero parameters and an empty input schema, so no parameter documentation is needed. The description correctly implies that invoking it requires no arguments, satisfying the baseline for parameterless tools.

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 starts with a specific verb and resource: 'List all wallets in the local keystore.' It further names the exact storage directory and the fields returned, distinguishing it clearly from sibling tools like wallet_create, wallet_export, or wallet_balance.

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 clear context that this is the tool for enumerating all locally stored wallets, with no parameters needed. It does not explicitly mention when not to use it or name alternatives, but for a zero-parameter list operation the intended context is obvious.

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