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

Annotations already mark readOnlyHint=true, and the description adds valuable behavioral nuance beyond that: the credit card liability warning, the 'unknown' handling when a statement has no balance, and the explicit note that categorizing/confirming/posting are human actions. This gives an agent important context not encoded in the schema.

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 dense and somewhat long, but each sentence carries meaningful content: position wording, exact fields reported, the credit card liability distinction, parity with the web UI, and the read-only boundary. No fluff, though it could be tightened.

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 needed completeness load: it names the report contents, the status categories, the backlog, the per-statement balances, and the warning about credit card figures. An agent has enough understanding to call the tool and interpret a returned snapshot.

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 has zero parameters and schema coverage is 100%, so the schema already exhaustively documents the input contract. Description therefore does not need to compensate for missing parameter documentation. Baseline 4 is appropriate.

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 a read-only bank reconciliation status report: GL balance versus latest statement closing balance, status counts, and per-statement tie-out. It is specific about the resource and scope, although it does not explicitly differentiate itself from sibling tools like bank_review_queue.

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 establishes clear context: it shows the same figures as the in-app Bank Reconciliation page and is READ-ONLY, implying it is for checking status, not taking action. However, it never explicitly says when to choose this over alternatives or names a sibling like bank_review_queue for the actionable side.

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