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

Beyond the read-only, open-world, idempotent annotations, the description adds strong behavioral context: matching is deterministic, based on end-to-end IDs and BigInt-exact amounts, facts are computed only from documents, and the tool returns a signed XDR-1 receipt. This tells the agent exactly how the tool behaves and why its verdicts can be trusted.

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 three dense sentences with no wasted wording. It front-loads the core reconciliation purpose, then lists verdicts and receipt behavior, so an agent can grasp the tool's scope immediately.

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 complex reconciliation tool with four optional inputs, full schema coverage, annotations, and an output schema, the description is complete enough. It explains accepted document types, matching logic, verdict categories, and receipt generation without redundantly detailing return structure already covered by the output schema.

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%, and each parameter already documents its role and alternatives (for example, nacha_ach instead of camt053_xml). The description adds useful matching semantics but does not provide additional parameter-level details beyond the schema, so the baseline of 3 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 states a specific reconciliation purpose: comparing pain.001/pacs.008 instructions against camt.053 statements or NACHA ACH files. It names the exact document types, matching keys, and verdict categories, which clearly distinguishes it from sibling validation tools such as iso20022_validate.

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 usage by specifying the input combinations (pain.001/pacs.008 versus camt.053/NACHA), but it does not explicitly say when to choose this tool over alternatives or when not to use it. No exclusions or alternative tool names are provided.

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