delete_dataset

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

With no annotations, the description must carry behavioral disclosure. 'Permanently' explicitly signals irreversibility, which is valuable for a destructive operation, but it omits other relevant facts such as required permissions, whether associated versions/files are deleted, and error behavior.

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 three words with no filler, and the verb and resource are front-loaded. Every word earns its place, with 'permanently' adding non-redundant behavioral meaning.

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?

For a destructive tool with no annotations, no output schema, and an undocumented required parameter, this description is too thin to be self-sufficient. It explains what action occurs but not what 'ref' must contain, what side effects are triggered, or what safeguards/authorization are needed.

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% and the only parameter 'ref' has an empty description. The tool description never mentions 'ref' or its expected format, so an agent must infer from the parameter name and tool context that it is a dataset reference; this is weak compensation for the missing schema documentation.

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 clear verb ('Delete'), a specific resource ('dataset'), and the critical qualifier 'permanently.' This distinguishes it from sibling tools like delete_model, delete_kernel, and update_dataset without needing to open their schemas.

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 is given about when to use this tool versus alternatives. It does not mention relevant conditions such as ownership, whether a dataset can be restored, or that update_dataset should be used for non-destructive changes.

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