getTransactionsForAddress

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

Annotations already indicate readOnlyHint=true, and the description adds the scope of 'to and from' but does not disclose pagination, return format, or any potential differences from other transaction tools. It adds some context beyond the name but little else.

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, concise sentence that conveys the core purpose without unnecessary words or restating the tool name.

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 lack of an output schema and the large number of similar sibling tools, the description is too minimal to fully inform an agent about what to expect. It does not explain what a 'transaction' includes, whether internal transactions are covered, or how this differs from getBulkTransactions or getWalletTransactionSummary.

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?

The description does not explain the parameters other than implicitly referring to the address. Schema coverage is only 33% (only address has a description), and authToken and chainName are left undocumented. The description fails to compensate for this gap.

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 states the tool retrieves transactions to and from a wallet address, using a specific verb and resource. It distinguishes from sibling tools like getERC20Transfers or getOneTransaction by indicating bidirectional transaction retrieval for an address.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that this is the general transaction fetcher for an address or that specific transfer types should use other tools.

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