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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: the filter is applied before the count, so 'total' is the filtered total and the pager reflects the narrowed set — a real semantic fact an agent could not infer from the schema. It omits read-only confirmation, pagination defaults, and auth requirements, so it is not complete.

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?

A large share of the text is a historical bug narrative with internal ticket references (ZET-285, ZET-150, ZEN-42) that do not help an agent invoke the tool. Meanwhile, genuinely needed content (what 'q' and 'status' filter on) is absent, so the space is allocated poorly rather than efficiently.

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 10-parameter, no-annotation, no-output-schema tool, the description leaves seven parameters undefined and says nothing about the shape of a returned journal entry or pagination behavior. What it does cover is deep but too narrow to make the definition callable with confidence.

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 0%, so the description must compensate, and it only documents 3 of 10 parameters (period_ids, untagged_subledger_control, origin). The ambiguous ones — 'q', 'status' (untyped string), sort/order/limit/offset — get no explanation at all, leaving most call semantics to guesswork.

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?

Opens with a specific verb+resource ('List journal entries'), which is enough to separate it from get_gl_journal_entry and the create/post/reverse siblings by name alone. It never explicitly names an alternative, and the bulk of the text is about filters rather than the tool's scope, 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?

Gives strong conditional guidance for individual filters ('period_ids narrows to specific fiscal periods, and is how a caller asks for one fiscal year', 'untagged_subledger_control=true narrows to...'), which borders on usage guidance. But it never says when to reach for this tool rather than global_search, list_gl_open_items, or get_gl_journal_entry, and gives no exclusions.

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