kaggle_kernel_output

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

The description claims 'Read-only fetch,' but the annotation readOnlyHint is false, indicating a contradiction. Additionally, while it mentions 'Log tail is untrusted-wrapped and truncated,' this positive detail is undermined by the inconsistency 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?

The description is concise at two sentences, front-loading the main action. It could be slightly more efficient by merging the second sentence, but overall it's well-structured.

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 presence of an output schema, the description should clarify what is returned beyond the generic 'output files and logs.' It lacks details on return structure and pagination, leaving gaps for a tool with no schema descriptions.

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%, so the description must explain parameters. It does not describe the 'kernel' or 'file_pattern' parameters, leaving the agent without guidance on how to specify them.

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 it downloads a completed kernel's output files and logs, and specifies it's a read-only fetch. This distinguishes it from sibling tools like kaggle_push_kernel or kaggle_kernel_status. However, it could be more specific about the exact output included.

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 does not provide guidance on when to use this tool vs alternatives, nor when not to use it. It only states it downloads from a completed kernel, but lacks explicit context for selection among many sibling tools.

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