Parse NACHA/ACH file

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

No annotations are provided, so the description carries the burden. It discloses validation behavior well: cross-checking record counts, hashes, and debit/credit totals, and reporting mismatches as 'issues'. It could add a bit more about error behavior for unreadable or malformed files, but the existing detail is substantial.

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?

Two tight sentences, each carrying essential information: the first defines the output structure, the second the validation behavior. It is front-loaded with the core action and resource. No filler or repetition.

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?

Given one parameter, no annotations, and no output schema, the description is remarkably complete: it lists the CSV JSON composition, the validation checks, and the reporting of issues. An agent can confidently call the tool knowing what input to provide and what to do with the result.

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?

There is only one parameter and its schema description is 100% complete ('Absolute path to the NACHA/ACH file on disk'). The tool description does not add anything about the parameter beyond the schema, but with full schema coverage 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?

States a specific verb ('Parses') and resource ('NACHA/ACH fixed-width file') and names the output structure explicitly (file header, batches, control). It also distinguishes itself from sibling summarize_nacha_file by emphasizing structured JSON extraction plus validation rather than summarization.

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 conveys the natural use case—get structured JSON from a NACHA file—but it does not explicitly contrast with summarize_nacha_file or state when the agent should choose parsing over summarizing. Usage context is implied clearly by the verb and output, but there is no explicit when/when-not guidance.

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