kaggle_dataset_preview

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

Describes behavior as safe, capped at 50 rows, width-limited, and untrusted content. Annotations show readOnlyHint false, which could imply a write operation, but description's 'safe preview' suggests read. No strong contradiction.

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 concise sentences front-load key information. Could improve structure slightly but is 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?

With output schema present, return values need not be described. Tool is simple and description covers core behavior and constraints. Some param details missing but acceptable for a preview tool.

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%, so description must compensate. It explains the 'n' parameter (max 50 rows) but does not explain 'dataset' or 'file'. Meaning of 'file' parameter is omitted.

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?

Description clearly states the tool previews first N rows of a dataset CSV with headers, dtypes, and capped rows. It addresses the user need 'What does the data look like?' and distinguishes from siblings like 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?

Description implies usage for quick previews without full download, using phrases like 'safe first-N-rows preview' and 'without dumping the whole file'. Context is clear but lacks explicit when-not-to-use or alternative tool names.

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