List output files from a Kaggle kernel session by supplying the owner username and kernel slug.
List output files from a kernel session.
Args:
user_name: Kernel owner username.
kernel_slug: Kernel slug name.
| Name | Required | Description | Default |
|---|---|---|---|
| user_name | Yes | ||
| kernel_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 provided. Description only states 'List output files' without disclosing read-only nature, error handling, pagination, or output format. The behavioral burden is on the description, which is minimal.
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?
Very concise: one-sentence description plus Args section. No extraneous words, but could be slightly more informative without losing brevity.
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?
Has output schema but does not explain return format. With 0% schema coverage and no annotations, the description is too sparse for a tool that lists files. Lacks details on behavior when session does not exist or when no output files are available.
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%, but the description adds meaningful context: 'Kernel owner username' and 'Kernel slug name'. This clarifies parameter purpose beyond the bare schema titles.
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 'List output files from a kernel session' with specific verb 'List' and resource 'output files from a kernel session'. It specifies the two required arguments, distinguishing it from sibling tools like kernel_output or kernel_session_status.
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 on when to use this tool versus alternatives. Does not mention scenarios where kernel_output or other list tools would be preferred, nor any prerequisites or caveats.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.