Cancel Dataset Download

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that cancellation is only 'requested' and applies to a running local job, but it does not state whether the request is asynchronous, whether the job is actually stopped, what happens to partial data, or what errors may occur.

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 a single compact sentence with no filler or redundant restatement of the title. Every word earns its place and the key constraint ('running', 'local') is front-loaded.

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 is simple with one parameter, so a minimal description is partially adequate. However, without annotations or an output schema, the description should have clarified the cancellation effect and expected outcome to be fully complete.

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% and the description does not elaborate on download_id beyond what the parameter name already implies. The ID is plausibly a download job identifier, but the description does not confirm its exact referent or format, leaving some ambiguity.

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 names a specific action ('request cancellation') and a specific resource ('running local OC dataset download job'), making the tool's purpose unambiguous. It also distinguishes itself from siblings like download_dataset and get_download_status by focusing on the cancellation workflow.

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 phrase 'running ... download job' implies the tool should be used while a download is active, but there is no explicit guidance about when not to use it or which sibling tool to prefer. Usage context is present only by implication, not direct instruction.

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