create_wallet

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

No annotations are provided, so the description must disclose behavioral traits. It states 'create' implying mutation but does not describe side effects, permissions, limits, error handling, or behavior on duplicates. The return type is mentioned but not detailed.

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 sentences, minimal and front-loaded. Every sentence adds value: purpose, input format, output type. 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?

Despite having a nested input schema and no annotations, the description is too brief. It lacks details on naming constraints, uniqueness, idempotency, or what WalletInfo contains. The output schema exists but is not shown; the description should compensate for this gap.

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 description coverage is 0%, so the description must compensate. It adds the concept of a 'list of wallet names', which is not explicitly in the schema's field names. However, it does not explain the nested structure of CreateWalletRequestContainer or the required 'name' field in detail, leaving some ambiguity.

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 new wallets' with a specific verb and resource. It adds that it expects a list of wallet names and returns WalletInfo, making the purpose clear. However, it does not differentiate from sibling tools like create_groups or create_dca_order, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or compare with sibling tools like create_groups or rename_wallets. Only parameter expectations are given.

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