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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond them: it discloses the auth requirement (a Cotlet API key with app access) and the downstream role of the returned ID.

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 what the tool returns, followed by purpose and usage. Five short sentences, each contributing something; no wasted filler, though it is slightly longer than strictly necessary.

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 no output schema, the description compensates by naming the returned fields and the auth requirement. Only minor gaps remain (no pagination hint despite limit/offset, no explicit note on volume).

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% (limit and offset are documented in the schema), and the description adds no syntax or format detail about them. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (list) and resource (ledger accounts / grootboekrekeningen) and even enumerates the returned fields (ID, code, name, category). It clearly distinguishes itself from mutation/creation siblings by explaining what it returns, though it doesn't explicitly contrast with the nearby get_ledger_balances 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?

Gives concrete when-to-use guidance: the ledger_id feeds create_invoice lines and create_mutation bookings, and instructs to 'look up the ID here instead of guessing a code.' That is a clear use context with a named alternative behavior, though there is no explicit when-not-to-use.

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