Fetch and save Kaggle kernel output files to a local directory. Specify the kernel reference and optional output folder or file pattern to retrieve specific results.
Download kernel output files
| Name | Required | Description | Default |
|---|---|---|---|
| ref | Yes | ||
| output_dir | No | ||
| file_pattern | No |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description names the core behavior (download) but adds no detail on side effects, authentication requirements, or failure modes. With no annotations available, the description carries the full burden and does not disclose whether this writes files to disk, what ref must refer to, or how output_dir is used.
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 concise in word count, but it is under-specified rather than appropriately sized. For a tool with three undocumented parameters, a single phrase omits essential information and is not an adequate definition.
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?
With no annotations, no output schema, and an empty input schema, this description is far from complete. Critical information about ref format, output_dir semantics, file_pattern behavior, and expected return values is missing, making reliable invocation impossible.
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 mentions none of the three parameters. ref, output_dir, and file_pattern are completely unexplained, so an agent cannot determine what values to supply or how these parameters affect the download.
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 a specific verb and resource: downloading kernel output files. However, it does not define what 'output files' means relative to sibling tools like kernel_files or kernel_logs, leaving some ambiguity about its exact scope.
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?
No guidance is provided about when to use this tool instead of alternatives such as kernel_files or kernel_logs. There are no prerequisites, exclusions, or context clues beyond the tool's name and the short description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.