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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context — the account types surfaced and the returned fields (IBAN, type, sync status) — but says nothing about pagination behavior, default limits, or auth, so it is adequate rather than rich.

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?

A single front-loaded sentence that defines the resource and its payload, followed by the endpoint mapping. No filler, though the endpoint reference is somewhat redundant for an agent that already has the tool bound.

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 full schema coverage and annotations, the description supplies the returned fields (IBAN, type, sync status) that substitute for the absent output schema. Only pagination/ordering behavior is left unaddressed.

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 each of the four parameters (embed, limit, offset, count_all) fully documented in the schema, so the baseline of 3 applies. The description adds no parameter-level detail such as default page size or paging guidance beyond what the schema already states.

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?

Names a specific verb (list) and resource (check accounts) and goes further by defining what a check account is — bank accounts, cash registers, and clearing accounts — plus the fields returned (IBAN, type, sync status). It is clearly distinct from the sibling get_check_account_balance, though it does not explicitly name that sibling.

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 context 'accounts sevdesk tracks payments on' implies when the tool is relevant, but there is no explicit when-to-use statement or exclusion relative to siblings like get_check_account_balance or list_transactions. Usage is left to inference.

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