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

With no annotations, the description carries the full burden and does so substantively: it discloses that reversed entries are included (both legs), drafts excluded, that the server carries running balance across pages, and the distinct semantics of page_opening_balance vs closing_balance/total_debit/total_credit. It omits any permission/auth or rate-limit note, so not a full 5.

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, then the important exclusions and balance semantics. Dense but nearly every clause earns its place; the field-naming detail is slightly heavy but justified by the absent output schema.

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 annotations and no output schema, the description steps up by explaining return-field semantics, paging continuity, and 404/422 error conditions. Only the undocumented limit/offset behavior and any auth prerequisites keep it from being fully complete.

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 0%, so the description must compensate. It adds real meaning for account_id (FY-scoping) and date_from/date_to (422 when from > to), but says nothing about limit, offset, or company_id, leaving half the parameters undocumented in both schema and prose.

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 resource ('One account's ledger (Kontoauszug)') and the exact content it returns ('every booking that touched it, in date order, with Soll/Haben and the running balance'). This is clearly distinguishable from siblings like list_gl_journal_entries or gl_trial_balance.

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?

Explains the selecting context well: account_id already fixes the fiscal year so no FY parameter is needed, posted AND reversed entries are included while drafts are not. It does not, however, explicitly name an alternative sibling tool or state when to prefer this over list_gl_journal_entries, leaving that to inference.

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