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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states what the result contains, including the reason for movement and the balance after each entry, but it does not disclose ordering, pagination, filtering, or the effect of the limit parameter.

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 a single, dense sentence with no filler or redundant content. It front-loads the core concept and earns its place by defining the tool's output in a compact way.

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 absence of an output schema and annotations, plus confusingly similar siblings, the description is insufficient for an agent to confidently select and invoke the tool. It explains the output concept but omits invocation semantics, parameter roles, and distinctions from wallet_movements or wallet_summary.

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 compensate by explaining the parameters. It alludes to an 'account', which maps loosely to the required owner parameter, but it gives no meaning for limit or network and does not explicitly state that owner identifies the account.

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 identifies the resource as ledger entries for an account and describes the content: what moved, why, and the balance after. It is more specific than a tautology and gives a distinct meaning, though it lacks an explicit verb like 'get' or 'list' and does not explicitly differentiate itself from wallet_movements or wallet_summary.

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 offers no guidance on when to use this tool versus the closely related sibling tools wallet_balance, wallet_movements, and wallet_summary. It only implies that the tool is for viewing full ledger statements, without explaining exclusions or alternatives.

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