Export expenses within an inclusive date range to a CSV file on disk and return its path.
Export expenses within an inclusive date range to a CSV file on disk and return its path.
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | Yes | End of the date range (inclusive), YYYY-MM-DD. | |
| start_date | Yes | Start of the date range (inclusive), YYYY-MM-DD. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It explicitly reveals that the tool writes a CSV file to disk and returns a path rather than inline data. It does not mention overwrite behavior, but the core behavioral contract is present.
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?
A single front-loaded sentence conveys the action, scope, output format, destination, and return value. Every word contributes meaning and there is no filler.
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 simple two-parameter tool with full schema coverage and an output schema, the description covers what is needed to invoke and interpret the call. The only notable omission is file-overwrite behavior, which is a minor gap.
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?
The input schema already fully documents both parameters with format and inclusivity. The description's phrase 'inclusive date range' adds no new parameter-level meaning, so the high schema coverage keeps this at baseline.
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 ('Export expenses'), along with the date range, output format (CSV), destination (disk), and return value (path). This clearly differentiates the tool from siblings like list_expenses or summarize.
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 makes the intended use case apparent: use this tool when expenses need to be exported to a CSV file on disk. It lacks explicit exclusions or named alternatives, but the context is clear enough for an agent to route correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.