Import CSV / Spreadsheet

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

Despite no annotations, the description discloses key behaviors: auto-detection of columns, transaction categorization, GST calculation, and supported bank formats. It doesn't mention side effects like duplicate handling or result output, but it goes beyond a minimal description.

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?

Three sentences, front-loaded with what the tool does, followed by value-add behaviors and supported formats. Every sentence contributes meaning with no fluff.

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 7-param tool with no output schema, the description explains the import process well, including auto-detection, categorization, and GST. However, it doesn't describe return values, error handling, or whether imported transactions are permanently added. This is a minor gap given the rich description.

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 has 100% coverage, so baseline is 3. The description adds meaning by explaining auto-detection (relevant to column override params) and GST handling (relevant to default_gst_included). This provides context not fully captured by the schema.

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 imports transactions from a CSV file, with specific use cases (bank statement, credit card, expense spreadsheet). It also supports multiple bank formats, distinguishing it from siblings like import_pdf and record_transaction.

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?

Clear context for when to use: CSV files from bank statements, credit card statements, or expense spreadsheets. No explicit exclusions or alternative tool names, but the use cases are well-defined and imply the appropriate scenario.

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