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

Annotations are empty, so the description must disclose behavior itself. It indicates the operation returns a list of accounts and provides account_fk for later use, but it doesn't state whether the operation is read-only, if it has side effects, or any rate limits. This is insufficient for a tool with no annotations, warranting a 2.

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 repeats the exact sentence 'Provides a detailed list of accounts in a wallet' twice, adding no value and wasting space. While the remainder is structured with @param and @return lines, the duplication is a clear defect. This reduces the conciseness score to a 2.

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 simple list tool with an output schema present, the description covers the basic purpose and parameters but lacks important behavioral details like pagination, read-only confirmation, or how to handle errors. It also doesn't mention the relationship to the verbose sibling tool, leaving the agent uncertain about which to choose. Given the empty annotations and the repeated sentence, the description is not fully complete, scoring a 2.

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 description provides clear @param documentation for all three parameters, explaining that api_key is the application's key, and token and wallet_fk are obtained from /access/login. This adds meaningful context beyond the schema's bare types and even indicates the source of the values. This fully compensates for the schema's 0% description coverage, earning a 5.

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 states a specific verb ('Provides a detailed list of accounts in a wallet') and identifies the resource (accounts within a wallet). It adds that each entry returns an account_fk for later use, which clarifies the output's purpose. However, it does not distinguish itself from the sibling tool wallet_accounts_list_verbose, so it gets a 4 rather than 5.

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 no guidance on when to use this tool versus alternatives like wallet_accounts_list_verbose or account_info. It implies the usage context (list accounts for a wallet) but doesn't state prerequisites or exclusions. The param docs reference /access/login for token and wallet_fk, but that's authentication info, not usage guidance.

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