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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only added behavior is the ordering guarantee (newest first) and the fact that line detail and reversal linkage are included — useful, but thin, and it says nothing about how many entries come back or how periods are scoped.

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 single front-loaded sentence with no filler; the resource, ordering, and payload contents all earn their place in under fifteen words.

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 no output schema, the description carries the burden of describing the return shape, and it does the minimum (lines and reversal included). It omits the fields on each entry line, the absence of any pagination/limit control given zero parameters, and whether 'adjusting' is a filter or a synonym for all journal entries.

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?

The tool takes zero parameters, so there is no per-parameter semantics to explain and the baseline of 4 applies. The schema is a closed empty object, matching the description's implicit 'list everything' behavior.

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?

Names a specific resource (adjusting entries) and adds scope details — newest-first ordering, includes lines and reversal markers. It stops short of explicitly distinguishing itself from the singular gl_entry or the sibling journal/ledger tools (gl_changes, core_journal), so the agent must infer that this is the list-all variant.

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?

Usage is only implied: an agent reading 'adjusting entries, newest first' will infer this is the read path for reviewing adjusting entries, but there is no explicit when-to-use statement, no prerequisite/period context, and no named alternative such as gl_entry for fetching a single entry.

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