payway_get_transaction_list

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

The description discloses some behavioral traits: a maximum date range of 3 days and a rate limit of 50 requests per minute. However, it does not mention pagination behavior, response format, or potential errors (e.g., exceeding the date range), leaving significant behavioral aspects untold. With no annotations, this partial transparency yields a neutral score.

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 packs essential information: the action, filters, and constraints. It is well-structured and front-loaded, with no unnecessary words or repetition.

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 existence of several sibling transaction tools, the description is somewhat incomplete. It does not specify the structure of the returned transaction list, whether summaries or full objects are included, or how to handle the optional parameters. It covers the core filtering intent but leaves contextual details (e.g., sorting, pagination behavior, response shape) unaddressed.

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 semantically covers the filter parameters (date, amount, status) but omits the 'page' and 'pagination' parameters entirely. Although the schema descriptions for status, date fields, and pagination provide some detail, the tool-level description does not clarify how pagination works or that 'pagination' is a page-size parameter. The 'max 3 days' constraint adds value beyond the schema, but overall coverage is partial.

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's purpose: 'List transactions filtered by date range (max 3 days), amount range, and status.' The verb 'List' and the object 'transactions' are specific, and the mention of filters distinguishes it from sibling tools like payway_get_transaction_details or payway_check_transaction.

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 provides no explicit guidance on when to use this tool versus alternatives. It mentions constraints like the 3-day limit and rate limit, but does not indicate when to prefer this over payway_get_transactions_by_merchant_ref or payway_get_transaction_details. Users are left to infer the appropriate use case.

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