list_transactions

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

With no annotations, the description carries the disclosure burden. It does add one meaningful behavioral trait: results are ordered newest first. It does not explicitly state that this is a read-only list operation or describe pagination/response behavior beyond what the schema hints at, but the tool name and 'list' semantics imply safe retrieval.

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 very short, contains no filler, and front-loads the resource and ordering. It is efficient, though it is a fragment rather than a complete sentence, so it slightly sacrifices completeness for brevity.

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?

There is no output schema and no annotations, so the description should provide richer context about what a payment transaction record contains and what the response looks like. It only states the resource and sort order, which is enough to guess tool selection but not enough to fully anticipate results or interpret the response.

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 description coverage is 100%, with clientid, limitnum, and limitstart each already documented. The description adds no parameter semantics, so it does not go beyond the baseline established by the schema.

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 identifies the resource ('payment transactions') and a key differentiator ('newest first'). However, it lacks an explicit verb and does not contrast with neighboring listing tools like list_invoices or list_orders, so it stops short of full sibling differentiation.

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 given about when to choose this tool over alternatives such as list_invoices or list_orders. The only implied usage is that it returns payment transactions, with no exclusions, prerequisites, or context about whether a clientid is expected.

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