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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is lower. It adds the underlying API endpoint and wildcard semantics, but says nothing about result ordering, pagination, or volume of transactions returned for an all-accounts wildcard, which is the main behavioral risk here.

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 tight sentences: the core purpose and wildcard rule come first, followed by the endpoint reference. No filler and nothing buried.

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 read-only list tool with a fully described five-parameter schema and no output schema, the definition covers what to call and how to scope it. The remaining gap is what the response looks like and how many rows an all-accounts wildcard may return.

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%, so all five parameters (including the date bounds and closing/opening toggles) are already documented. The description restates the accno wildcard rule and adds the "x matches any digit" detail, a small value-add over the schema's 10xx example, but nothing beyond the baseline.

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 ("List ledger transactions of one account") plus the wildcard scope, so an agent can distinguish it from the chart/customer/invoice siblings. It does not explicitly name a sibling it supersedes, which keeps it short of a 5.

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 parenthetical "use x for all accounts" gives a concrete usage pattern for the wildcard, which is helpful guidance. There is no explicit guidance on when to prefer this over sibling tools such as trial_balance or list_payments_since, so usage context is only implied.

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