Download a dataset to a file

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=true. The description adds a real behavioral fact beyond them: 'Never overwrites an existing file', which is important safety context for a write tool and slightly qualifies the idempotency hint. It still omits auth requirements, overwrite-error behavior, and remote/network implications of openWorldHint.

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 short sentences, front-loaded with what is saved and where, then formats, then the overwrite caveat. No padding, no restatement of the title, every sentence carries 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?

No output schema exists, yet the description covers the essential call-time facts (what is written, format choices, no-overwrite guarantee) and the schema supplies defaults for path and format. It could still say what the call returns (e.g. the written path) or note large-dataset/network behavior, hence not a 5.

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 coverage is 100%, so the baseline is 3. The description adds semantic labels to the enum values that the schema lists bare ('jsonl (original)', 'messages (OpenAI chat)'), which genuinely helps an agent pick a format; the code and path parameters are left entirely to 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?

Specific verb+resource: 'Save a whole ContexteTech dataset to a local file', with an explicit enumeration of output formats. It implicitly separates itself from load_resource ('whole dataset' written to disk rather than loaded), but never names an alternative, so the differentiation is inferential rather than stated.

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?

'ready for fine-tuning or evaluation' gives a rough purpose context, which implies when you'd reach for this tool. However there is no explicit when-to-use vs load_resource/search_resources guidance, no prerequisites, and no exclusions.

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