list_account_transactions

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

With no annotations, the description carries the full behavioral burden. It usefully discloses pagination behavior and the exact trimmed return fields, but says nothing about permissions/auth, default date window behavior, or read-only nature, so disclosure is partial.

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?

Front-loaded with purpose, then filters, then return shape in three tight sentences. The return-field enumeration is somewhat long but genuinely informative given there is no output schema, so it earns its space.

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 9-parameter list tool with no output schema, the description compensates well by listing return fields and pagination, and filters are covered by the schema. The main gap is the absence of any routing guidance against the many sibling list/get tools.

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 coverage is 100%, so both schema and description fully document the 9 parameters. The description only restates the filter categories (date range, status, search, merchant category) without adding format or default details beyond what the schema already gives (e.g., YYYY-MM-DD, default windows). 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 ('Retrieve a paginated list of transactions') scoped to 'a specific Mercury account', which is more precise than the generic sibling list_transactions. It stops short of naming that sibling or get_transaction to differentiate directly, so an agent must infer the split.

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 when-to-use guidance or alternatives are given. The sibling set contains list_transactions, get_transaction, and get_treasury_transactions, but the description never says which to pick or under what conditions; the only usage signal is the implicit 'specific account' scope.

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