tuik_download_data

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

With no annotations, the description carries the transparency burden. It discloses that the tool writes a CSV file to a specified output path, which is a side effect. However, it does not mention potential overwriting, required permissions, network access, or error behavior—context that would be valuable for a download/write tool.

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 compact and well-structured: a single purpose sentence followed by a concise args list. It contains no filler, and every line adds useful information.

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?

The tool has a moderate complexity of 5 parameters (2 required), and all are documented with examples. An output schema exists, so return values are likely self-explanatory. The description lacks explicit usage alternatives but covers the essentials for invoking the tool correctly.

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 zero descriptions, but the description fully compensates by explaining each parameter with concrete examples, including the three-part dataflow_id format, output_path example, key syntax, and start/end period semantics. This adds substantial meaning beyond the raw schema.

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 downloads a full TUIK SDMX dataset and writes it as a tidy CSV file. This is a specific verb+resource+output, and it distinguishes itself from sibling tools like tuik_get_data by emphasizing 'full' dataset download and CSV output.

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 usage for downloading full datasets to CSV files via the argument explanations, but it does not explicitly state when to use this tool versus alternatives or offer exclusions. No sibling tool is referenced, so the guidance is only implicit.

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