Download Dataset Locally

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

With no annotations, the description carries the full transparency burden and does well: it reveals background execution, the local root directory, the auth_required retry flow, the no-credentials-in-chat rule, and license prerequisites. It stops short of explaining how to poll or interpret the success status beyond the auth_required case.

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?

Two dense sentences with no filler. The first sentence front-loads the core operation and location; the second packs the auth handling, license requirement, and security constraints without redundancy.

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?

Given no annotations and no output schema, the description covers the important behavioral context: background execution, destination root, auth handling, and security guardrails. The main gap is the lack of an explicit success response/polling note, such as telling the agent to use get_download_status, though this can be inferred from the background-download wording and sibling tools.

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 67%, but the description adds meaningful semantics: destination is understood as relative to OC_DOWNLOAD_ROOT, accept_license must reflect explicit user review, and dataset_id is an identifier rather than an arbitrary URL. This goes beyond the schema's basic property descriptions.

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 opening phrase 'Start a background download inside OC_DOWNLOAD_ROOT' expresses a specific verb, resource, and scoping location. It clearly distinguishes the tool from sibling status/plan/cancel tools by emphasizing that this is the action that initiates the download rather than checking or managing it.

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 gives clear when-to-use and when-not-to-use signals: it requires explicit license acceptance, and it explicitly rejects arbitrary source URLs and shell commands. It does not name sibling alternatives such as get_dataset_download_plan or get_download_status, so the routing is slightly less explicit than a 5.

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