list_transactions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only says 'List recent transactions' — it doesn't mention whether this is a read-only operation (likely, but not confirmed), the ordering (e.g., by date descending), or the default limit behavior. It doesn't disclose any side effects, authorization requirements, or rate limits.

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 short sentence, which is extremely concise and easy to read. It front-loads the core purpose, but it is arguably under-specified — being too terse may sacrifice needed detail, but for such a simple tool, it is appropriate.

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 tool has one optional parameterable, no output schema, and no annotations, the description is too sparse. It doesn't explain the response format, the time window for 'recent' (e.g., last 30 days), or how this relates to search_transactions. For a listing tool, an agent would benefit from knowing if results are paginated or if it supports filters beyond limit.

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 provides no additional meaning for the 'limit' parameter — it doesn't clarify what the limit applies to or its effect on the response. However, having only one parameter with a default of 10, the description is partially sufficient; an agent can infer that limit controls the number of transactions returned, but it would be better to state that explicitly.

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 'List recent transactions' states the verb and resource, but it is too brief and somewhat vague — it doesn't specify the recent time window or any filters, and with several transaction-related siblings (list_transactions, get_transaction, create_transaction, search_transactions), it doesn't clarify how this differs from them. It is a clear but minimal statement.

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 gives no guidance on when to use this tool versus alternatives like search_transactions or get_transaction. There are no exclusions or alternatives mentioned. An agent would have to infer that this is a simple listing function, but it doesn't explicitly state that search_transactions is for complex queries or that get_transaction is for a single record.

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