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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds nothing behavioral on top. It does not say what happens for an unknown id, whether the ledger could be deleted/inactive, or what the response contains, leaving the description essentially a restatement of the endpoint.

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 short fragments, front-loaded, with no padding. The second fragment ("GET /v1/ledger/{id}") largely duplicates the tool name and endpoint metadata, which is minor waste but not bloat.

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 simple single-record read with 100% schema coverage this is nearly adequate, but there is no output schema, so nothing tells the agent what a ledger object contains or how a not-found case is signaled. Minimal but with a visible gap.

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% and the single 'id' parameter is already documented in the schema, including the hint that it comes from eboekhouden_list_ledgers. The description contributes no additional parameter meaning, so the baseline of 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?

"One ledger account" plus the endpoint GET /v1/ledger/{id} identifies both the resource and the singular-retrieval verb, so an agent can tell this is a single-record fetch rather than a list. It does not explicitly contrast with the closest siblings (eboekhouden_list_ledgers, eboekhouden_get_ledger_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?

There is no statement of when to call this instead of eboekhouden_list_ledgers (fetch many) or eboekhouden_get_ledger_balance (balance for a ledger). The singular phrasing implies the distinction, but the description offers no explicit routing guidance or prerequisites.

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