Summarize NACHA/ACH file

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

With no annotations provided, the description carries the full safety burden. It clearly states it parses and returns a summary, implying a read-only operation, and notes that it reports validation issues. However, it does not explicitly state side-effect-free behavior or potential error conditions on malformed files.

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?

A single, tightly packed sentence that front-loads the verb and resource, then enumerates specific output elements. No wasted words, and the critical exclusion is stated compactly.

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 simple one-parameter tool with no output schema, the description adequately specifies its return content with field-level detail. It falls just short of being fully complete by not describing the result structure or behavior on invalid files, though those gaps are minor.

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 the single file_path parameter is well-documented in the schema. The description does not add meaning beyond the schema, which is fine at the baseline of 3.

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 action ('Parses... and returns') and explicitly lists the summary contents: batch count, total entries, total debit/credit amounts, SEC codes, and validation issues. The phrase 'without dumping every field of every record' clearly differentiates it from the sibling parse_nacha_file.

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 explicitly frames when to use this tool: when a condensed summary is desired rather than full record-level detail. The contrast 'without dumping every field' effectively communicates the when-not and implicitly routes to the sibling for detailed extraction.

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