dataset_delete

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

No annotations provided. The description says 'Delete' but gives no details about permanence, required permissions, cascading effects, or whether deletion can be undone. For a destructive action, this omission is significant.

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 but includes parameter lines that duplicate schema content, reducing conciseness. It could be trimmed to a single sentence without the parameter block.

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 that this is a destructive tool with no output schema details (though output schema exists, it is not explained), no behavioral annotations, and minimal parameter info, the description is incomplete for safe and correct usage.

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%. The description restates parameter names (owner, dataset_slug) without adding meaning beyond what the schema provides. No explanation of what constitutes a dataset slug or any constraints.

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 explicitly states 'Delete a dataset.' which clearly indicates the action and resource. It distinguishes from sibling tools like dataset_create or dataset_get, but lacks details about scope or consequences.

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 such as dataset_create_version or model_delete. No prerequisites or conditions for deletion are mentioned.

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