Parses an e-Fatura CSV export into individual documents and creates a booking proposal for each, so exported invoices can be prepared for bookkeeping.
Parse an e-Fatura CSV export into documents, each with a booking proposal.
| Name | Required | Description | Default |
|---|---|---|---|
| csv_path | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It says the tool parses CSV data and produces documents with booking proposals, but does not disclose whether it writes to the system, whether proposals are persisted, whether the file is only read, or what happens on malformed input.
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 with no wasted words and front-loads the action and result. It is appropriately sized for a one-parameter parsing tool.
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?
The output schema exists, so return values do not need to be explained. However, with no annotations and only a terse statement, the description leaves important context unstated, including whether the operation mutates state by creating booking proposals and how it relates to sibling tools.
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 one required parameter, csv_path, with 0% schema description coverage. The description clarifies that the input is an 'e-Fatura CSV export', which adds useful meaning beyond the bare parameter name, but it does not specify path format, encoding, or expected CSV structure.
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 states a specific verb and resource: 'Parse an e-Fatura CSV export into documents, each with a booking proposal.' It is clear what the tool does and what it produces, though it does not explicitly distinguish itself from the sibling 'reconcile_efatura' or 'extract'.
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 implies the tool is for parsing e-Fatura CSV exports, but it gives no explicit when-to-use guidance, prerequisites, or alternatives such as 'reconcile_efatura' or 'extract'. An agent must infer the selection context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.