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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds non-obvious behavior beyond that: node-paid lines carry a null tx_hash and point at cause_tx/cause_method, amounts are wei strings with exact decimal WAN alongside, and reconcile performs a genesis-to-now sum against the node balance.

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 definition is dense and front-loads the resource and line structure before moving to edge cases and pagination. Every sentence carries information, though the middle sentence is long and slightly overloaded with the null-tx_hash exception details.

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?

With no output schema, the description does the heavy lifting and adequately describes the returned line shape, the null-tx_hash exception, pagination via next_cursor, and the reconcile mode. Missing only the address input format and any indication of error or empty-ledger behavior.

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%, so the description must carry the parameter burden, and it largely does: limit is bounded 1 to 100, cursor is next_cursor from the previous answer, reconcile triggers a genesis sum compared to node balance. The address parameter is only implied ('of a Wanchain address') with no format guidance such as hex/checksum requirements.

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 names a specific resource (the WAN ledger of a Wanchain address) and spells out exactly what a ledger line contains: signed amount, counterparty, transaction, and post-transaction balance. That content profile is distinctive enough to separate it from siblings like get_address_activity or get_address_flows without opening any schema.

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?

It gives usable mechanics (paginate with limit/cursor taken from next_cursor; set reconcile true to sum from genesis and compare against the node balance), which implies when to use those options. However, it never states when to prefer this tool over the many sibling address tools, and no alternative is named or excluded.

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