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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds useful behavioral context beyond annotations: results are ordered 'newest period first' and include unmatched line counts per statement. It does not cover pagination or limits, but the output schema and low complexity reduce the need.

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?

The description is a single efficient sentence, front-loads the verb and resource, and packs ordering and unmatched-count behavior without redundancy. Every clause earns its place.

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 simple read-only list operation with an output schema and safety annotations, the description is largely complete. It conveys what is listed, the ordering, and the key metric, though it could strengthen context by mentioning the optional accountId filter or routing to the singular get_statement tool.

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 the baseline is 3 even without extra parameter explanation. The description adds no parameter-specific meaning, and the schema only describes each parameter as 'UUID value wrapper,' leaving the role of optional accountId implicit.

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?

The description clearly states the action ('List'), the resource ('bank statements imported for reconciliation'), and adds meaningful specifics: newest period first and unmatched line counts. This distinguishes it from nearby siblings like accounting_get_statement and accounting_get_list_journal_entries.

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?

The description implies its use case: when you need an overview of imported bank statements and their reconciliation progress. However, it does not explicitly name alternatives or state when not to use it, such as when a single statement's full detail is needed via accounting_get_statement.

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