search_bank_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 helpfully declares 'Read-only' (substituting for a readOnlyHint) and the 'append-only' immutability of the underlying evidence, which is genuine value. It does not, however, disclose return format, pagination behavior beyond schema defaults, 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?

Two tight clauses with zero waste; the scope and the read-only nature are both front-loaded. Nothing is padded.

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 read-only search tool with full schema coverage and no output schema, the description is nearly complete, conveying scope and mutation safety. It could mention pagination/result shape, but the schema handles parameters well enough that this is a minor gap.

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%, so the schema already documents all 12 parameters thoroughly (defaults, formats, examples). The description only restates filter categories (account, date range, direction, match status, duplicates) without adding syntax or format detail. Baseline 3 is appropriate.

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 (Search) and a precisely scoped resource (imported bank transactions), then enumerates the filter dimensions. This is clearly distinguishable from siblings like search_bank_accounts (different resource) and get_bank_transaction (single-record fetch).

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 list of filter dimensions implies the use case (finding transactions by account/date/direction), but there is no explicit when-to-use guidance and no mention of alternatives such as get_bank_transaction for retrieving a single transaction. Usage is inferred rather than stated.

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