dataset_export

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

Annotations already mark the operation read-only and non-destructive. The description adds useful behavioral context beyond that: the result is a time-limited download link rather than the export itself, and it can target either the latest version or a specific frozen version. This is meaningful additional disclosure despite not detailing link expiry or auth requirements.

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?

A single, front-loaded sentence states the action, the output, the input formats, and the version behavior with no filler. Every clause earns its place.

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 read-only retrieval tool with simple parameters and no output schema, the description covers the key return concept (time-limited download link) and the version selection behavior. It stops short of describing error cases or link expiry duration, but those are minor for the tool's complexity.

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 input schema already describes both parameters, so the baseline is 3. The description goes further by explaining the accepted formats for 'dataset' (slug, owner/slug, ul:// URI) and clarifying that omitting 'version' yields the latest export while supplying it selects a frozen version. That adds real semantic value beyond the 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 opens with a specific verb and resource: 'Get a time-limited export download link for a dataset.' It names the accepted reference forms (slug, owner/slug, ul://owner/datasets/slug URI) and the two retrieval modes (latest export or frozen version), which clearly sets it apart from sibling export operations like export_create, export_status, and exports_list.

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 conveys how to specify a dataset and choose between latest and frozen exports, but it does not explicitly state when to prefer this tool over export_create, export_status, or exports_list. Usage context is clear, but exclusions/alternatives are left to the agent to infer from sibling names.

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