delete_dataset

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

The description discloses that the deletion is permanent and cannot be undone, adding crucial behavioral context beyond the annotations' destructiveHint. It also specifies the backing endpoint, providing technical clarity. This is consistent with the annotations (no 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?

The description is concise—two sentences with the key fact front-loaded. The endpoint reference adds specificity without verbosity, and there is no redundant information.

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 simple delete operation, the description covers the essential behavioral context (permanence) and the endpoint. It does not describe the response or explicitly guide usage alternatives, but given the simplicity and the annotations covering idempotency, it is largely complete.

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?

The schema has 0% description coverage, and the description only implies the parameter via the endpoint path ({dataset_id}). It does not explain the format, source, or any constraints of dataset_id, which is insufficient for a tool with an undocumented parameter.

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 the action ('Permanently delete') and the specific resource ('a training dataset'), distinguishing it from sibling delete tools like delete_deployment. It also references the exact REST endpoint, leaving no ambiguity about what operation is performed.

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 implies usage context—use this tool when deleting a training dataset—but does not explicitly mention alternatives or when not to use it. It provides a clear scope (training dataset) without exclusion, which is adequate but not fully explicit.

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