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

With empty annotations, the description carries the transparency burden. It discloses that the tool retrieves balances for unsupported tokens, that account_fk is a database ID not an address and may not be 0, and lists authentication parameters. However, it does not explicitly state read-only behavior or potential errors/limitations beyond those parameters.

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, which wastes space. The @param format is clear and front-loaded, but the duplicate sentence and vague @return ('a json object') detract. Overall it is acceptable but not taut.

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?

The tool is a simple balance lookup with four required params, all explained. The description clarifies key nuances (account_fk type, asset_id forms, authentication tokens) and notes it covers unsupported tokens. The output schema exists, so the vague return description is acceptable. It does not discuss blockchain-specific behavior, but that is not necessary for basic use.

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 coverage is 0%, but the description's @param block adds substantial meaning for all four parameters: api_key is application-level, token is a wallet API token from /access/login, account_fk is an integer database ID with specific constraints, and asset_id can be a contract address. This fully compensates for the schema's lack of descriptions.

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 the tool retrieves a token balance on the blockchain, using a specific verb ('Retrieves') and resource ('token (asset_id) balance'). It also specifies input types (asset_id, token, or contract address) and notes it works for any token even unsupported by Netfluid, which differentiates it from sibling tools.

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?

Provides context on when to use it: when you need a token balance for any asset, including unsupported tokens. It does not explicitly name alternatives or exclusions, but the context is clear enough. Since netfluid__crypto_balance exists as a sibling, a direct comparison would have been stronger.

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