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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses that the operation is read-only ('display only, no action is taken') and states the mnemonic/private-key precedence rule. It omits other relevant behavior: whether secrets are transmitted or persisted server-side, error behavior when neither key is supplied, and any rate or security constraints.

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 truncated mid-word ('The suppo'), so content is both repeated and lost. The @param block merely restates schema property names. Structure is disorganized and not front-loaded beyond the one repeated line.

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?

There is no output schema, so the description owns the return contract, yet it offers only '@return: a json object' with no indication of what fields come back (address, balances, derivation path). Combined with the truncated sentence and undocumented blockchain_fk domain, this leaves meaningful gaps for a 4-parameter crypto tool.

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, and it does document all four parameters with real detail: api_key is 'allocated to your application,' blockchain_fk selects the chain, private_key must be urlencoded, and mnemonic keywords are space-separated. Encoding and delimiter formats are non-obvious facts that the bare schema does not carry. It does not explain valid blockchain_fk values.

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: recovers/derives a blockchain wallet from a private key or mnemonic, plus the important qualifier that it is 'display only, no action is taken.' It does not distinguish itself from the near-identical sibling netfluid__access_recover or netfluid__wallet_mnemonic, which keeps it below a 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?

Gives conditional guidance on inputs — mnemonic takes precedence over private key, and one or the other must be provided — which is useful operating context. However, it never says when to choose this tool over sibling recovery tools such as access_recover or wallet_mnemonic, so tool-selection guidance is implied at best.

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