Internal Account Transactions

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the bar is lower; the description still adds real context beyond them: newest-first ordering, that the response carries the current balance and deposit address, that amounts are SUN strings, and the wallet-signature auth requirement. It stops short of describing pagination behavior.

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?

Four short sentences, front-loaded with the resource and contents, then use case, then auth requirement. No filler, though the 'Read-only' trailing clause partly duplicates readOnlyHint.

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?

An output schema exists, so return shape needn't be spelled out, yet the description helpfully flags balance/deposit address and SUN units. Auth prerequisite is stated. The only meaningful omission is pagination guidance for limit/offset.

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 only 50% (limit has 'Default 20', offset has no description at all), and the description says nothing about pagination, page size caps, or offset semantics. It does not compensate for the gap it inherits from the schema.

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: lists the TRX ledger of the logged-in user's internal account, and enumerates the entry types (deposits, order payments, refunds) plus ordering (newest first). This distinguishes it from order-centric siblings like tronsave_internal_order_history, though no sibling is named explicitly.

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?

'Use to reconcile spending after orders' gives one concrete scenario, and 'Requires a wallet signature identity' states a prerequisite. However, it never says when to prefer this over tronsave_internal_order_history or tronsave_list_orders, nor any exclusion conditions.

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