import_csv

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not mention what happens to existing data, whether duplicates are skipped by default, what the import outcome looks like, or any error conditions. This lack of detail leaves significant behavioral ambiguity for an agent.

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 a single sentence, making it highly concise and front-loaded with the core purpose. Every word serves a function, and there is no unnecessary verbosity.

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 the tool has 7 parameters, no output schema, and no annotations, the description is markedly incomplete. It fails to explain the import behavior, return values, potential side effects, or any prerequisites, leaving an agent without sufficient context to use the tool correctly beyond basic invocation.

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?

Although the input schema provides descriptions for all 7 parameters (100% coverage), the description adds no additional meaning beyond the schema itself. The schema already documents each parameter, so the description's value here is redundant.

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's function as importing transactions from a CSV file, using a specific verb 'Import' and identifying the resource 'transactions' and source 'CSV file'. This distinguishes it from sibling tools such as `analyze_csv`, which likely analyzes rather than imports.

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 provides no guidance on when to use this tool versus alternatives such as `create_transaction` or `analyze_csv`. It lacks any context about scenarios where bulk CSV import is appropriate or prerequisites like file format.

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