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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: newest-first ordering, page size of 1-100, the next_cursor-to-cursor pagination contract, and the requirement for an API key with app access.

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 the core purpose, but visibly redundant: 'newest first' appears in two consecutive sentences and the opening sentence largely restates the title. The extra fields list is useful but the repetition costs efficiency.

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 carries the return-value burden and does so by describing item fields and matched invoices. It also covers pagination and auth, leaving it nearly complete for a read-only list tool, though the 'id' and 'journal' filters mentioned are not present in the schema's parameters, which is a minor inconsistency.

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 the baseline is 3. The description goes slightly beyond the schema by explaining the cursor round-trip ('pass next_cursor back as cursor for the next page') and clarifying the date/bank-account filter scope, which adds meaning to those parameters.

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 (lists) and resource (bank transactions) and enumerates the fields returned (label, amount, currency, categories, matched invoices). It doesn't name any sibling tool for contrast, but the purpose is unambiguous and distinct from match_transaction/categorise_transaction.

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?

Implies usage by spelling out the filtering constraints ('filters transactions by id, bank account, journal and date only'), which hints at when this list view is appropriate. However, it never states when to prefer this tool over siblings like pennylane_match_transaction or when-not to use it, so guidance is only implied.

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