extract_transactions

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

With readOnlyHint=false already signaling a possible write, the description adds real clarity: rows are written out only when `output` ends in .xlsx or .csv. This conditional-write disclosure is valuable context beyond the annotations. It does not cover overwrite behavior, keeping 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?

Two compact sentences, no filler, with the core action front-loaded and the conditional write behavior stated second. Every sentence earns its place.

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?

An output schema exists, so return values need not be described, and the conditional write is covered. The gap is the `overwrite` parameter, whose semantics (behavior when the target exists) are undocumented anywhere, leaving a mutation-adjacent behavior ambiguous.

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 0%, so the description must compensate across three parameters. It meaningfully explains `output` (extension-driven file write) and implies `path` is the source document, but `overwrite` is left entirely undocumented in both schema and description.

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 ('Read') and resource (bank statement / invoice list) plus the produced structure (rows of date / label / amount). It clearly distinguishes this extraction tool from generic siblings like read_text or ocr, though it doesn't explicitly name them.

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?

Naming 'bank statement or an invoice list' implies the document types this tool is meant for, giving implied usage. However, no when-not conditions or explicit alternatives (e.g., ocr, read_text) are provided, leaving the agent to infer the boundary.

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