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

Annotations are empty, so the description carries the full burden. It does disclose a genuinely useful behavioral trait ('This may take some time to complete') and identifies the credentials required, but it says nothing about read-only status, pagination, result size, or rate limits for a call it warns is slow.

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 opening sentence is duplicated verbatim, and the body is JSDoc leaked from source code (@param/@return) rather than prose. The '@return: a json object' line consumes space while conveying nothing.

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 three-required-param, no-annotation, no-output-schema tool with a nearly identical sibling, the definition omits the essentials: how it differs from wallet_accounts_list, what the response contains beyond 'a json object', and whether results are paginated. Only the credential provenance and latency warning are complete.

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 schema documents nothing beyond types. The description's @param tags compensate meaningfully, especially by stating token and wallet_fk come from /access/login and api_key is the application key — provenance the agent could not get from the schema.

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 clear verb+resource ('detailed list of accounts in a wallet') plus the notable scope of crypto balances being included. However, it never distinguishes this tool from the near-identically named sibling netfluid__wallet_accounts_list, leaving the 'verbose' variant unexplained.

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?

There is no when-to-use guidance, no prerequisites beyond the param tags, and no mention of the alternative netfluid__wallet_accounts_list — which is the single most important routing decision for an agent here. The agent must infer the choice from the name suffix alone.

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