export_receipts_csv

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

Discloses it returns Base64-encoded CSV but not behavioral traits like side effects or auth needs. Annotations absent, so description carries full burden; basic disclosure but gaps remain.

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-line description with clear purpose, Args, and Returns sections, no unnecessary words.

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?

Covers key aspects: input expected, output format. Could mention what DATEV-compatible entails or size limits, but adequate for a simple export tool.

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 description adds 'List of receipt extraction results (from extract_receipt)' to the receipts parameter, clarifying its source and type, which is valuable beyond the schema's bare definition.

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?

Clearly states the tool exports extracted receipt data as DATEV-compatible CSV, distinguishing it from sibling tools like export_receipts_xlsx.

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?

Implies usage after receipt extraction but lacks explicit guidance on when to choose CSV over other formats or any exclusions.

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