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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: results are returned 'newest first', filtered by date or description, and the auth requirement ('Cotlet API key with access to this app') is disclosed. Ordering and auth needs are genuine additions.

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-loads the purpose and keeps to four sentences with the key use-case in the middle. Slight redundancy between the first sentence ('with date, description and lines') and the third ('shows its number, date, description and lines'), which costs a point but the text is otherwise efficient.

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 usefully enumerates the returned fields (number, date, description, lines) and notes ordering and auth. Combined with the fully documented pagination/date parameters, an agent has enough to call it correctly, though it doesn't mention result volume or rate limits.

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 (limit, cursor, to_date, division, from_date, description) is already documented in the schema. The description only implies date/description filtering and adds no syntax or format detail beyond the schema, so the 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) and resource (general journal entries in a division), and clarifies scope with return fields (number, date, description, lines). It also names the related sibling book_journal_entry, so an agent can distinguish this read operation from the write operation in the same family.

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?

Explicitly gives a use case with the alternative named: 'Use it to check for an existing entry before book_journal_entry.' This is clear when-to-use guidance tied to a specific sibling. It stops short of a full 5 because it never states when not to use the tool or other alternatives.

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