export_to_csv

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

With no annotations, the description carries full behavioral burden. It mentions writing to a local CSV file, but does not disclose side effects like overwriting behavior, directory creation, or execution time. The word 'directly' adds some context but minimal detail.

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 clear sentence with no wasted words, front-loading the verb 'Export' and the resource.

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 export tool, the description covers the core purpose, but lacks details on file handling behavior and relationship to similar tools. Annotations are absent and output schema exists but doesn't compensate for missing usage guidance.

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 schema provides complete descriptions for all three parameters with 100% coverage. The tool description does not elaborate on parameters beyond what the schema already states, so it adds no additional semantic value.

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 exports a Eurostat dataset to a local CSV file, using a specific verb and resource. It distinguishes from siblings like export_multiple_datasets and download_dataset_to_sql by specifying a single dataset to CSV.

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 use case (exporting a single dataset to a local CSV) but does not explicitly mention alternatives or when not to use. Sibling tools like download_dataset_to_sql and export_multiple_datasets exist, but the description offers no guidance on choosing among them.

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