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

Annotations already declare readOnlyHint=true and openWorldHint=false, and 'READ-ONLY' merely restates that. However, the description adds substantive behavioral context the annotations cannot: the meaning of each status bucket, that NOT_EXPLAINED is an 'honest remainder', that STATEMENTS_DONT_JOIN signals a missing/duplicated statement, and crucially the CREDIT CARD liability sign convention (negative = money owed). That domain semantics is genuinely valuable beyond structured fields.

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 an extremely dense single block, essentially one sprawling sentence with only a final 'READ-ONLY.' tacked on. The core purpose is front-loaded in the opening clause, but the intervening enumeration of every status, bucket, and edge case is hard to scan and much of it could be structured or trimmed. Length is not justified by what it helps an agent decide.

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 and no parameters, the description carries the full burden of describing the return shape, and it does so thoroughly: balances and differences per account, rowCounts by status, backlog with pairedInBooks, reconcilingItems with signed effects, notOnStatementNotInBooks, and per-statement tie-out. An agent can anticipate the response structure. What it lacks is any pointer on when this tool is the right choice relative to sibling reconciliation tools.

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 per the rubric the baseline is 4. There is no parameter syntax for the description to document and it adds nothing spurious.

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 identifies the resource (per-bank-account reconciliation status) and enumerates what the status comprises: GL vs statement balance, rowCounts by status, backlog, reconcilingItems, and per-statement tie-out. It is specific about the returned content, but it never distinguishes itself from the sibling bank_reconciliation_report or bank_review_queue, both of which sound like overlapping reconciliation views.

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?

There is no explicit statement of when to call this versus bank_reconciliation_report, bank_review_queue, or the in-app page it references. The only guidance is the implicit framing 'Where each bank account stands on reconciliation', which conveys context but no selection criteria or exclusions.

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