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

Annotations already cover the read-only safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds a non-annotation behavioral detail: it requires the user's Cotlet API key with access to this app, and it is scoped to a single division. It does not mention pagination behavior, which is only implied by the cursor param.

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 and efficient overall, but the first two sentences are near-duplicates (both say ledger accounts of a division with code and description), which is minor redundancy that could be trimmed.

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 read-only list tool with a fully documented schema and no output schema, the description covers purpose, usage and auth sufficiently. It could be strengthened with a note on paging via cursor, but nothing essential is missing.

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 all four params (limit, query, cursor, division) are already documented. The description only lightly reinforces the query param ("search by code or part of the description") and the division scoping, adding little beyond the schema. 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 verb (Lists) plus resource (ledger accounts / general ledger accounts) and scope (of one division, with code and description). It also names book_journal_entry as the downstream consumer, so agents can situate it in the Exact Online workflow without opening a schema.

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?

Gives clear context: search by code or part of the description to locate a single account, and use the returned code in book_journal_entry. It stops short of explicit when-not-to-use or an alternative sibling for listing accounts, but the usage window is well established.

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