kaggle_delete_dataset

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

Annotations already mark destructiveHint=true, but the description adds crucial context: irreversibility, requirement for explicit config and confirm_token. This goes beyond annotations, though it could detail more about consequences like deletion of associated resources.

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 wasted words. The first sentence states purpose and irreversibility; the second explains prerequisites. Efficient and 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?

Given the destructive nature and special config, the description covers key aspects: operation, irreversibility, config flag, token requirement. Output schema exists, so return values are not needed. Lacking parameter format explanation holds it back from a 5.

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?

With 0% schema description coverage, the description should explain parameter details. It only mentions confirm_token as a requirement but does not clarify what 'dataset' expects (e.g., name or ID format). The agent has insufficient guidance to fill parameters correctly.

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 tool deletes a dataset and all its versions irreversibly. It uses strong, specific language that distinguishes it from sibling tools like kaggle_create_dataset or kaggle_download_dataset.

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 explicitly states the tool is disabled unless the server is started with KAGGLE_MCP_ENABLE_DESTRUCTIVE=1 and requires a confirm_token, never defaulting to yes. This provides clear when-to-use and prerequisites, though it doesn't mention alternatives like preview_delete_dataset.

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