Get account balances

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and idempotency are covered. The description adds the scoping constraint (trading accounts only) and the weight-1 rate-limit cost, which is useful, but it omits return shape, pagination, and whether the account must be authenticated. A 3 reflects modest added value over annotations.

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?

Two short sentences, front-loaded with the verb and resource, then the scope caveat and rate-limit weight. No filler. The title/description duplication ('Get account balances' repeated) is minor waste, keeping it below a 5.

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 zero-parameter read tool with no output schema, the main missing piece is what the response contains (asset list, available/frozen fields) and any auth prerequisite. Annotations cover safety, but the description leaves the agent without a sense of the return payload or account context.

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?

With zero parameters, the baseline is 4. There is no parameter surface to document, and the description correctly does not invent any, so nothing is misleading. The scope qualifier is the only parameter-like information needed.

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 ('Get account balances') and narrows scope to 'trading account balances (excludes bot and earn accounts)'. That scoping distinguishes it from pionex_wallet_get_balance_full and pionex_earn_*_balances siblings, though it does not explicitly name them. Clear but not maximally differentiated.

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 exclusion of bot and earn accounts implies when this tool is appropriate versus the earn/wallet siblings, but no explicit when-to-use or alternative routing is provided. Usage is implied by the scope note rather than stated.

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