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

Annotations only declare readOnlyHint=true; the description adds ordering semantics, the fact that the first page is usually sufficient, the scale risk ('accounts can have thousands of transactions'), and how the returned cursor is meant to be used. That is substantial behavioral disclosure well beyond the annotation.

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, no filler, front-loaded with purpose and the anti-pattern warning before the sibling reference. Every sentence carries distinct guidance.

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?

Despite no output schema, the description covers what comes back (newest-first page plus cursor) and the paging contract, so an agent knows how to call it and what to do with the result. Nothing material is missing for this read-only list tool.

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 address, network, limit and cursor are already fully documented in the schema, including that cursor fetches the next/older page. The description adds the 'newest first' framing but no syntax or format detail beyond the schema, so baseline 3 applies.

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 ('Transaction history of any entity'), enumerates the entity kinds (account, validator, component, resource), and fixes the ordering ('newest first'). It also explicitly distinguishes itself from get_transaction, so an agent can separate them without opening either 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?

Gives explicit when-to-use ('the first page already shows the most recent activity, which is what users almost always want'), an explicit when-NOT-to ('do NOT keep paging to the end'), and names the alternative tool for the single-transaction case. The condition that triggers further paging is spelled out.

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