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

Annotations only cover readOnly/openWorld, so the description carries the rest and does so well: item shape, RAW WEI warning, selector-is-not-a-name, omit-rather-than-guess, and the time.iso/time.iso_unavailable contract. These are exactly the data-contract facts an agent needs to avoid downstream errors.

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?

Purpose is front-loaded and each sentence conveys contract information, so the length is largely earned given there is no output schema. It is dense and slightly repetitive in emphasis ('RAW WEI, not ether and not token units'), and the 'no second alias key' aside reads as defensive, minor deductions.

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 thoroughly covers return values, which is the main completeness burden. It leaves the pagination mechanism unexplained (the schema exposes only pageSize, yet 'every continuation' is referenced) and says nothing about auth or rate limits for an openWorld indexer call.

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 chain/address/pageSize are already documented, and the baseline is 3. The description adds no parameter-level meaning beyond what the schema states (it never addresses pageSize semantics or chain slug format directly).

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 first sentence gives a specific verb, resource, and scope: recent transactions for one address on one chain, newest first. That framing inherently distinguishes it from getTransaction (single tx), getInteractions, and getLogs, so an agent can route without opening another 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?

Usage is implied by the stated scope rather than stated outright. There is no explicit when-to-use vs alternatives (getTransaction, getInteractions) and no pagination/continuation guidance, though the Sui note ('transactions SENT BY the address') is a useful invocation caveat.

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