datasets_delete

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

The description adds 'soft-delete' behavior beyond annotations, which already set destructiveHint=true. However, it does not elaborate on what 'soft' means (e.g., recoverability, visibility, cascade effects), leaving significant behavioral gaps for a destructive operation.

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 a single concise sentence with no superfluous words. It is front-loaded with the verb and key detail about identifier types. Perfect structure for minimal length.

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 good schema coverage, annotations, and single parameter, the description covers basic purpose but omits return behavior, error states, and the practical implications of soft-delete. For a destructive tool, more completeness is expected.

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?

Parameter 'dataset' has 100% schema coverage with a description nearly identical to the tool description. No additional syntax, constraints, or examples are provided. Baseline 3 is appropriate as the description adds no value beyond the schema.

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 ('soft-delete') and the resource ('dataset'), covering multiple identifier types (id, slug, username/slug, ul:// URI). It effectively distinguishes this tool from sibling tools like datasets_create or datasets_list.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, post-deletion effects, or related tools like restore. It lacks explicit 'when-to-use' or 'when-not-to-use' context.

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