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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for adding what those can't: the exact matching algorithm order (EndToEndId first, then amount+date tolerance with currency), the determinism guarantee, and the receipt's contents (digests, rule declaration, execution_hash). It does not cover failure behavior (malformed XML, duplicate EndToEndIds, overflow of exceptions), which keeps it short of a 5.

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?

It is front-loaded with the action and the pipeline composition, then moves to returns and scope. The single dense sentence with nested parentheticals is heavy prose, but nearly every clause adds decision-relevant information rather than repeating the schema or title.

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, and the description fully compensates by enumerating the return surface (matches, exceptions, reconciliation receipt with named digest fields). Combined with the algorithm and the explicit prepare-only scope, an agent has everything needed to call it correctly.

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 coverage is 100% and defaults are documented, so the baseline is 3. The description still adds real semantics by naming the CSV header contract (EndToEndId,Amount,Currency,Date) and explaining that amount_tolerance/date_tolerance_days participate together in the secondary match pass, which the schema alone does not convey.

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+resource pair (match a camt.053 statement against a CSV expectation set) and immediately names the two pipelines it reuses (camt053_parse checks, WORKBOOK-1 CSV parser). It is clearly distinguishable from the sibling camt053_parse (parse only) and workbook_csv_parse (CSV only) because it explicitly composes both plus a match engine.

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 closing clause 'Prepare/hash/receipt only; per-exception disposition receipts are the browser workbench's interactive follow-on' draws a clear boundary on when this tool stops. It also signals via 'same schema-subset checks as camt053_parse' that parse-only work belongs elsewhere, but it never names a sibling alternative for the pure-parse or pure-CSV case explicitly.

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