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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the closing 'Read-only' confirms without contradicting. The description adds real behavioral context beyond annotations: newest-first ordering, inclusion of pending/unaccepted transactions, and a 30-day default window.

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?

Front-loaded with purpose and source in the first clause, then return fields, then data-source caveat, then default range. Every sentence carries distinct information with no redundancy.

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?

With no output schema, the description usefully enumerates returned columns (date, account, description, merchant, money out/in, currency, category) and states the default time window, which is everything an agent needs to call and interpret this read tool.

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 coverage is 100%, so all five parameters (to, from, search, account, company) are already documented in the schema. The description restates the 30-day default range but adds no syntax or semantics beyond what the schema provides, so the baseline of 3 applies.

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+resource (list bank transactions) and immediately scopes it to what 'the bank itself shows on the connected bank and card accounts,' explicitly distinguishing bank-feed data from QuickBooks books data. An agent can tell this apart from the many books-based list/search tools without opening the schema.

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?

Clearly frames the data source ('Read from the bank, not from QuickBooks') and notes pending/unaccepted feed items are included, which tells the agent when this tool is the right source. It stops short of naming an alternative sibling (e.g., find_bank_transactions_not_in_books) or stating when NOT to use it.

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