get_wallet_token_balance

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

No annotations are provided. The description merely states it 'gets' balances, implying a read operation, but does not disclose any behavioral traits such as rate limits, caching, or error conditions.

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 is very short (two sentences) and front-loaded, but the second sentence is nearly redundant. It is not verbose, but could be more efficient.

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?

Given the complexity of the nested input and the presence of an output schema, the description lacks detail about the return structure and fails to provide context for using this tool among many siblings.

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%, and the tool description does not add meaning beyond what is already in the schema. It repeats that it expects a WalletTokenPairsContainer but does not clarify parameter formats or relationships.

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 'Get the balance for a list of wallet/token pairs', which specifies the action and resource. However, it does not differentiate from other similar balance queries like get_stake_balances, missing sibling differentiation.

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 only mentions input and output types ('Expects a WalletTokenPairsContainer, returns a list of WalletTokenBalance'), but provides no guidance on when to use this tool versus alternatives, or any exclusions.

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