Download statement CSV

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

The annotations already declare readOnlyHint=true, and the description adds key behaviors: never overwrites existing files (returns FILE_EXISTS), returns byte count when saving to path, truncates inline at 100KB with a truncated flag. No contradictions.

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 concise (3 sentences) and front-loaded with the main action. It could be slightly more structured, but it is efficient and clear.

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?

Despite no output schema, the description covers return values (byte count, truncated flag, FILE_EXISTS) well. It does not detail CSV field names, but that is acceptable given the context of statement data.

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 description adds critical context beyond the schema: mutual exclusivity of invoice_number vs date range, absolute path requirement, parent directory must exist, and no overwrite behavior. This meaningfully aids agent understanding.

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 clearly states the tool downloads statement line items as CSV, distinguishing it from siblings like download_statement_invoice (likely PDF) by specifying the format and the two filtering modes (invoice_number vs date range).

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 explains when to use invoice_number vs date range, and when to use save_to_path vs inline (for large exports). It does not explicitly compare with sibling tools but the instructions are clear for intended use.

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