Get account transactions

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

No annotations are provided, so the description must carry full burden. It states 'Read-only' indicating non-mutation, but fails to disclose behaviors like pagination, sorting, rate limits, or how parameters like windowHours and page affect results.

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 concise: two sentences that efficiently convey purpose, read-only nature, and usage guidance without any superfluous words.

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 6 parameters with no schema descriptions, no output schema, and no annotations, the description is incomplete. It lacks details on pagination, filtering, result format, and edge cases, which are essential for proper tool invocation.

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?

With schema description coverage at 0%, the description adds no meaning beyond the schema. Parameters like address, direction, valueOnly, windowHours, page, and limit are unexplained, leaving the agent to infer from names alone.

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 does a read-only chain-wide Explorer DB transaction lookup for one account, specifying it can be sender, recipient, or both. This distinguishes it from sibling tools like get_block_transactions or get_session_transactions.

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 description explicitly advises using this tool instead of XDaLa session tools for account-wide transaction history, providing clear guidance on when to use it. It lacks explicit exclusions for other scenarios but effectively directs the agent.

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