kaggle_dataset_push

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It does reveal a size constraint, but it omits important details like whether existing datasets are overwritten, what the 'force' option does, and what side effects or authorization requirements apply.

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 short and front-loads the core action. The second sentence about size limits is relevant and not wasteful, though the overall under-specification prevents a perfect score.

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?

An output schema exists, so return-value explanation is not required, but the description is incomplete for safe and correct invocation. It lacks parameter semantics, usage context, auth expectations, and the behavior of the force flag.

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 compensate for documenting parameters. It only loosely implies 'local_path' through 'local folder' and gives no meaning for 'dataset_slug', 'title', or especially 'force'.

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 a specific verb and resource: 'Upload a local folder as a Kaggle dataset.' This clearly differentiates the tool from siblings like kaggle_kernel_push and kaggle_dataset_check by naming both the action and the target.

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 gives no guidance on when to use this tool versus kaggle_dataset_check or kaggle_kernel_push. It also fails to mention prerequisites such as Kaggle authentication or whether the dataset slug must already exist.

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