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

With no annotations, the description carries the full behavioral burden. It discloses that account_fk is a database integer ID, may not be 0, and comes from /wallet/accounts_list, and that the return is a json object. However, it does not describe authentication requirements beyond the parameter names, error behavior, or return structure in any detail.

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 first sentence is duplicated verbatim, wasting space. The @param and @return blocks are front-loaded and information-dense, but the duplication and vague '@return: a json object' reduce efficiency.

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 3-parameter tool with no output schema and no annotations, the description covers parameter meaning and sources reasonably well. However, it does not explain the shape of the returned balance, which would be important given the absence of an output schema.

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 documents all three required parameters: api_key's purpose, token's source via /access/login, and account_fk's type, allowed range, and origin. This adds substantial meaning beyond the bare schema types.

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 and resource: 'Returns a crypto wallet address balance associated with an account_fk.' It distinguishes the resource as a wallet address balance, which separates it from some siblings, but it does not explicitly contrast with the very similar sibling netfluid__crypto_token_balance.

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 explicit when-to-use guidance or alternatives. It only notes that account_fk is provided by /wallet/accounts_list, which is a prerequisite rather than usage direction.

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