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

readOnlyHint=true already declares the safety profile, so the description needn't carry it. It adds the filter capability set and the underlying endpoint, but says nothing about pagination behavior, default result size, or ordering that an agent might need.

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 sentences with the resource and filter set front-loaded. 'bank payments in and out' marginally duplicates what only_debit/only_credit already express, a small 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?

For a read-only list tool with no output schema and fully documented params, the description covers purpose and filter scope adequately. It omits mention of paging fields (limit/offset) and embed, though those are covered by 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% (12 params, each documented including limit range and ISO date guidance), so the schema already does the work. The description restates filter categories but adds no syntax or defaults beyond it.

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 (check-account transactions), and clarifies the domain as 'bank payments in and out'. It does not explicitly name how it differs from siblings like sevdesk_list_check_accounts or sevdesk_get_check_account_balance, so it stops short of a 5.

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 enumerated filters convey implied usage (narrow by account, booking state, date, party, purpose), but there is no explicit when-to-use guidance or routing to alternatives such as get_check_account_balance for balance queries.

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