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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds the useful scope detail that all three transaction directions are returned, but says nothing about pagination behavior, result ordering, or default result size (beyond the schema's page/per_page).

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 compact sentences, front-loaded with the purpose and ending with the concrete API endpoint. No filler; every element earns its place.

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 filtered list tool with no output schema, the description plus full schema coverage gives an agent enough to call it correctly. It could mention return shape or paging expectations, but that is a minor gap given the schema.

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 every parameter (page, per_page, search, date_from, date_to, bank_account_id) is already documented in the schema. The description adds no parameter-level detail such as date-range interaction or how search matches, so 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 'List' and resource 'bank transactions', and the parenthetical enumerates the three subtypes (money in, money out, transfers), which sharpens the resource. It does not explicitly differentiate from the nearest sibling, kledo_get_bank_balances (balances vs. transactions), but the resource is unambiguous on its own.

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?

Usage is implied by the resource name and the transaction-type list, but there is no explicit when-to-use or when-not guidance and no named alternative. An agent must infer that this is the tool for enumerating transactions rather than balances.

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