Permanently delete a Kaggle kernel by providing its reference. Clean up your workspace by removing unwanted or obsolete kernels from the platform.
Delete a kernel permanently
| Name | Required | Description | Default |
|---|---|---|---|
| ref | Yes |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. 'Permanently' does disclose the most important trait, irreversibility, but it does not mention required permissions, cascading effects on associated files or versions, or failure modes. This is adequate but incomplete for a destructive operation.
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 four-word sentence with no filler. The action is front-loaded and the critical qualifier 'permanently' 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?
The operation is simple and the action is clear, but the required parameter is completely undocumented and there is no output schema or annotation to fill the gap. An agent would need external knowledge of the API to know what to pass as 'ref'.
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 only parameter, 'ref', has an empty description, and schema description coverage is 0%. The description never explains what 'ref' refers to, whether it is an ID, slug, or full URL, so an agent cannot determine how to fill the required parameter.
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 states a specific verb, 'Delete', and a clear resource, 'a kernel', while adding 'permanently' to convey finality. This distinguishes it cleanly from sibling delete tools like delete_dataset, delete_model, and delete_model_version.
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?
There is no guidance on when to use this tool versus alternatives such as update_kernel or toggle_kernel_visibility. The permanence hint is present, but there is no explicit warning about prerequisites, ownership, or when deletion should be avoided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.