List files in a Kaggle dataset by providing owner and slug. See file names and structure for your analysis.
List files in a dataset.
Args:
owner: Dataset owner username.
dataset_slug: Dataset slug name.
| Name | Required | Description | Default |
|---|---|---|---|
| owner | Yes | ||
| dataset_slug | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states 'List files', implying a read operation. There is no disclosure of pagination, rate limits, or any behavioral traits beyond the obvious.
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 extremely concise with two sentences plus a parameter list. It is front-loaded with the purpose and wastes no words.
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?
For a list tool, the description omits critical details like whether results are paginated, sorted, or limited. While an output schema exists, behavioral gaps (e.g., no mention of file listing behavior) reduce completeness.
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 description lists each parameter with a brief explanation (e.g., 'owner: Dataset owner username'), adding meaning beyond the bare parameter names in the schema. With 0% schema description coverage, this significantly aids the agent.
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 'List files in a dataset' with a clear verb and resource. However, it does not differentiate from sibling tools like dataset_download_file or datasets_list, which could cause confusion.
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 provides no guidance on when to use this tool versus alternatives (e.g., dataset_download or dataset_download_file). No context on prerequisites or preferred scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.