list_transactions

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

Annotations already declare the operation read-only and idempotent, so the description does not need to restate safety. It adds the wallet scope, included categories, and sort order, which is useful, but it does not disclose pagination, response shape, or any limits. This matches a safe read tool with modest added behavior.

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?

A single sentence front-loads the verb and resource, adds concise parenthetical detail about transaction categories, and ends with ordering. Every word earns its place; there is no repetition of schema or annotation values.

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?

For a zero-parameter read-only list tool, this description is nearly complete: it states scope, content categories, and ordering. It falls just short of perfect by not mentioning pagination or the return-value shape, though those are less critical for selecting and invoking the 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?

There are zero parameters and the schema coverage is 100%, so there is nothing for the description to document. The baseline of 4 applies because no parameter meaning is missing.

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 a specific operation ('List every transaction') on a specific resource (the account's wallet), enumerates included transaction types, and specifies ordering ('most recent first'). This distinguishes it from sibling get_transaction and list_invoices by scope.

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 scope is clear, but the description never says when to choose this over get_transaction or list_invoices, nor does it state exclusions. Usage is implied ('every transaction on wallet') rather than explicit.

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