list_transactions

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description goes well beyond these by explaining ordering, inclusive date bounds, default status, amount sign conventions, transfer labeling, untrusted description data, and the scaffold's lack of live access. This is strong behavioral disclosure with no contradiction.

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 composed of short, information-dense sentences with no filler. Critical behavioral facts are front-loaded, and every clause adds value, from ordering to data trust.

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 rich annotations, an output schema, and a straightforward read operation, the description covers the essential behavior: pagination, sorting, date inclusivity, default status, sign conventions, transfer labeling, security guidance, and environment limitations. Nothing critical is missing for an agent to call this correctly.

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 0%, so the description must compensate for parameter meaning. It adds useful semantics for dates ('inclusive'), status ('Posted only by default'), and pagination ('one bounded page'), but it does not explain accountId, categoryId, page, or pageSize beyond what the schema already shows. The compensation is incomplete.

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 starts with a clear action ('Read one bounded page') and supplements it with transaction-specific details like amounts and transfers, making the tool's purpose evident. It does not explicitly name 'transactions' in the description or differentiate from siblings by name, but the resource is unambiguous through context.

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 implies usage context: use it to read a single bounded page of transactions, newest first, with posted status by default. However, it provides no explicit guidance about when to prefer this tool over siblings like list_accounts, list_categories, or get_budget_summary, and it offers no exclusions.

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