Export to CSV

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

With no annotations, the description carries the full behavioral burden. It usefully discloses path-safety rules: relative paths only, confinement to the data folder, and a required .csv extension. It does not mention overwrite behavior, whether directories are created, or what happens when constraints are violated.

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 two focused sentences with no wasted wording. It front-loads the purpose and then provides the path-safety constraints in a compact, scannable form.

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 one-parameter export tool with full schema coverage and no annotations, the description covers the purpose and critical path-safety rules. It is nearly complete, though it could mention overwrite behavior or the shape of the result for the caller.

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 schema already documents the exportPath as a relative path inside the data folder. The description adds meaningful invocation constraints beyond the schema, especially the explicit .csv extension requirement and reinforced path-safety rules.

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: exporting every logged donation to a CSV file in the data folder. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools like list_donations, totals, or quarterly_summary.

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?

Usage is implied by the scope 'every logged donation' and the CSV export purpose, suggesting a full export rather than a filtered view. However, there is no explicit guidance on when to choose this tool over alternatives such as list_donations or quarterly_summary.

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