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

With no annotations, the description carries the full behavioral burden, and it discloses a genuinely non-obvious trait: the from/to window scopes only the per-entry counts, while cross-month gap detection remains global. That asymmetry is the kind of thing an agent could not guess. It still omits auth/permission requirements and the return shape.

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-loaded with the purpose, then the scoping rule and its limit in two tight sentences. The stray 'Reconciliation summary banner.' lead is close to redundant with the title-like name, but the rest earns its place with no padding.

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?

There is no output schema, so the description must convey return content; it does name the key fields (counts, gaps, missing_periods) but does not enumerate the fields fully or explain company_id. Adequate but with clear gaps for a 3-parameter report 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 0%, so the description must compensate. It explains from/to semantics well (booking_date window, mirroring the grid filter) and reveals their partial effect on the result, but says nothing about the required company_id parameter or the expected date format.

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 body states a concrete verb+resource: it returns a reconciliation summary containing per-entry bank-entry counts (total/matched/missing-invoice) plus cross-month coverage (bank_accounts gaps, missing_periods). The opening line 'Reconciliation summary banner' is thin on its own, but the following sentences make the output content unambiguous. It does not, however, distinguish itself from near-neighbours like get_bank_status or list_bank_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?

It explains what the optional from/to do and that they mirror the /bank-entries grid filter, which implies usage for month-filtered views. But it never states when to call this rather than list_bank_entries, get_bank_status, or list_bank_accounts, nor any prerequisites beyond the required company_id.

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