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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds that results are imported records and the semantic of the linked flag. It omits pagination behavior and total/next_page structure, which matters for a 12-param paged listing tool.

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?

Three short sentences, front-loaded with what the tool returns before the usage hint and endpoint. The trailing 'GET /bank/transactions' is mild filler that doesn't help an agent decide or call.

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 list tool with fully documented params and no output schema, the description is adequate but thin: it doesn't describe the response envelope (pagination, total count, next_page) that the page parameter references, leaving an agent to infer result shape.

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% with clear enum docs for type and order, so the schema carries the parameter burden. The description reinforces only the linked semantics (reused from the schema) and mentions no parameter beyond that. Baseline 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 enumerates the returned fields (amount, date, counterparty, linked-to-document status), which distinguishes it from siblings like invbg_list_bank_accounts or invbg_list_payments. It stops short of naming a close alternative explicitly, but the domain is unambiguous.

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?

Adds a clear reconciliation use case with the key rule 'linked=false = unmatched', which is genuinely actionable. However, it gives no when-not guidance and doesn't contrast with invbg_list_payments or invbg_list_bank_accounts for overlapping needs.

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