kaggle_delete_model

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

The description highlights irreversibility and the need for an environment variable and confirmation token, which adds behavioral context beyond the destructiveHint annotation. No contradictions with annotations.

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 sentences, no fluff. Every word adds value: irreversibility, environment variable condition, and token requirement. Highly efficient.

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 that output schema exists and annotations are present, the description covers key behavioral aspects (irreversibility, destructive guard, token prerequisite). It could briefly explain how to obtain the model ID, but overall it is complete enough for a destructive action.

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 0%, and the description only mentions confirm_token in context but does not describe the 'model' parameter or its format. This leaves the user guessing how to specify the model, which is insufficient for a 2-parameter tool with no schema 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 description clearly states the action 'Delete a model' and emphasizes 'IRREVERSIBLE', distinguishing it from other tools. The resource (model) is unambiguous, and the irreversibility contrasts with preview or other non-destructive tools.

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?

Explicitly states that the tool is disabled unless KAGGLE_MCP_ENABLE_DESTRUCTIVE=1, and requires a confirm_token from kaggle_preview_delete_model. This provides clear when-to-use and prerequisites, distinguishing it from non-destructive operations.

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