wallet_list

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

No annotations are provided, so the description carries the full burden. It implies a safe read operation and that only agent-usable wallets are returned, but it says nothing about whether locked wallets appear, whether addresses are included, or how large the result set can get. Adequate but thin for a no-annotation 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?

Two short sentences, with the core purpose front-loaded. The second sentence is a promotional tip rather than invocation-relevant information, which slightly dilutes focus but costs little.

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 with no output schema, an agent still needs to know what each wallet entry contains (name? address? index?) to plan the next call. The description omits that, leaving a real gap even at this low complexity.

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 takes zero parameters and the schema is an empty object, so there is nothing to document. The description correctly implies the result is unfiltered by any input, which is the only semantic that matters here.

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?

States a specific verb and resource: 'List all wallets available for the agent to use.' That distinguishes it from get_wallet_info and wallet_status, which operate on a single wallet, though the description never names those siblings explicitly to make the contrast airtight.

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 phrase 'available for the agent to use' implies the context (agent-scoped enumeration) but gives no explicit when-to-use guidance versus wallet_status, get_wallet_info, or credentials_list. The tip points to earning_opportunities, but that is a next-step recommendation rather than a disambiguation of alternatives.

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