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

readOnlyHint=true already tells the agent this is a safe read. The description goes further by disclosing the exact shape of returned records, the valid category codes, and the pagination contract, which are not in the annotations. Missing are auth/permission notes or rate-limit behavior, keeping it below a 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 resource identity, then return fields, then the id reuse hint and paging rule in a tight sequence. No filler sentences. The parenthetical category enumeration is long but functional.

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 output schema, the description correctly compensates by enumerating the returned fields. The pagination contract and id-reuse guidance round it out. Only the absence of any filtering/usage caveats (e.g., how code/match interact) keeps it short of a 5.

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 the schema already documents all five parameters thoroughly (including the match enum and limit bounds). The description reinforces the next_offset/offset linkage and category values but adds little the schema doesn't already say. 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 resource with its Dutch synonym ('ledger accounts (grootboekrekeningen)') and enumerates the returned fields (id, code, description, category), so the agent knows exactly what this list contains. It doesn't explicitly differentiate from siblings like eboekhouden_get_ledger or eboekhouden_list_ledger_balances, but the purpose is unmistakable.

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?

'Use the id as ledger_id in other tools' and 'Paged: pass next_offset as offset' give real usage context. However, there is no explicit when-to-use-this vs get_ledger / list_ledger_balances, so the guidance is implied rather than spelled out.

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