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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only.' adds nothing beyond structured data. The description does contribute real behavior: newest-first ordering, per-transaction action and balance-change content, and the cursor-paging mechanic. It omits what happens when nextCursor is absent (end of history), which matters for a paginated tool with no output schema.

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?

Three short sentences, front-loaded with what the result contains before the pagination mechanics. The only wasted element is 'Read-only.', which merely restates the readOnlyHint annotation and could be dropped.

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 carries the burden of describing returns, and it does sketch them (actions plus balance changes per transaction) along with ordering and paging. The main gap is the unspecified end-of-pagination condition, a minor omission for a 3-parameter read tool whose schema is fully documented.

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 100%, so the baseline is 3, but the description adds value by explaining how the opaque `before` value is obtained (the returned nextCursor from the prior page) rather than just what it is. It still leaves `limit` and `address` entirely to the schema, which already covers them well.

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 the specific resource (an Olympia account's transactions) and adds two concrete traits: ordering (newest first) and per-item contents (actions and balance changes). It does not distinguish itself from adjacent siblings such as olympia_list_transactions_by_date, get_address_transactions, or olympia_get_account_funds_flow, which is what keeps it from 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 only usage guidance is the pagination instruction ('pass the returned nextCursor as `before`'), which is helpful but procedural rather than selective. There is no statement of when this tool is preferable to the date-based listing sibling or the generic address transaction tool, so an agent must infer the choice.

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