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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description nonetheless adds real behavior beyond them: newest-first ordering, the unit convention (amounts are SUN strings), the additional fields returned alongside the ledger, and the authentication prerequisite ('Requires a wallet signature identity'). It stops short of describing failure modes or empty-ledger behavior, which keeps it below a 5.

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?

Five tight sentences, front-loaded with the core operation and payload before moving to alternatives, pagination and the auth caveat. Parenthetical exemplars (deposits, refunds) and the sibling names each carry information; nothing is redundant.

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 two-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: scope, ordering, units, auth requirement, pagination mechanism, and disambiguation from the three nearest siblings. No material gap remains.

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 100%, with both parameters fully documented in the schema including defaults and bounds (max 50). The description only adds 'Page with offset/limit', which restates rather than extends the schema, so the baseline 3 applies.

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 first sentence names a specific verb (list) and resource (TRX ledger of the logged-in user's internal account), enumerates the entry types covered (deposits, order payments, refunds), states ordering (newest first), and names the extra payload (current balance, deposit address). It is immediately distinguishable from tronsave_internal_order_history and tronsave_get_internal_account.

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 an explicit use case ('reconcile spending after orders') and routes to the correct alternatives by name with the condition that selects each: order history tools for the orders themselves (including the API-key vs isOnlyMyOrder distinction), and tronsave_get_internal_account for balance alone. This is when/when-not/alternatives all in one place.

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