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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds genuinely new behaviour: row-per-position granularity, the 0/1 debit-credit encoding, and that cancellations are filtered out by default. No contradiction with annotations.

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?

Three tight sentences; the record identifier and row granularity come first, then filters, then the exclusion rule. The field enumeration is a bit list-like but each item conveys the shape of the result for a tool with no 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 14 optional parameters and no output schema, the description compensates well by naming the returned fields, the debit-credit encoding, and the default cancellation filter. An agent has enough to call this correctly and interpret the reply.

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 every parameter is already documented with ranges, patterns and defaults. The description only restates the filter set in prose, adding no format or syntax detail 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 the specific resource (accounting postings, record ACCDOC_GET) and the exact granularity ('one row per posting position'), plus enumerates returned fields. An agent can distinguish this from collmex_get_account_balances or collmex_list_invoices 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 concrete filtering axes (fiscal year, account, cost centre, customer, vendor, invoice, document date range) and a default-behaviour rule ('Cancelled postings are excluded unless asked for'). It lacks explicit routing against siblings such as get_account_balances, which is why it falls short of 5.

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