export_dataset

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

With no annotations, the description carries the disclosure burden. It clearly states that two output artifacts are produced (CSV and provenance sidecar), which is useful, but it omits operational details such as whether existing files are overwritten, whether the dataset is mutated, and what the sidecar contains.

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?

One sentence, no filler, and the key output detail is front-loaded. The parenthetical variable list earns its place by specifying exactly what 'analytic dataset' means.

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 export tool this is close to adequate, but without annotations or an output schema it should have explained filename semantics and the sidecar's role/location. Missing behavioral context prevents a higher score.

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 description coverage is 0%, so the description needed to explain dataset_id and filename. It gives no parameter-specific meaning; the filename parameter and its default are left entirely undocumented.

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 uses a specific verb and resource: 'Write the analytic dataset ... to CSV plus a provenance sidecar.' It also names the exact variables included, making the scope unmistakable and clearly differentiating it from build_dataset or survey_* siblings.

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?

There is no explicit when-to-use or alternative guidance; the intended use as the final export step is implied by the wording and sibling context. It doesn't name exclusions or explain how it relates to build_dataset/describe_dataset.

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