# Deleting tools are not marked non-destructive

**Tools that delete, overwrite, cancel, revoke or reset must set destructiveHint: true; with false, clients run them without a confirmation prompt, and both directories treat that as incorrect annotations.**

Check `annot-delete-marked-safe` · Annotations (both directories) · default severity: blocking · rubric 2.1.0. Last verified against OpenAI plugin guidelines, section 6.3 on 2026-11-18.

## What fails

The name reads as deleting, overwriting, cancelling, revoking or resetting, but the tool sets destructiveHint: false, so Claude would not prompt before calling it. Both platforms ask for true here; OpenAI adds that being able to undo the action does not justify false. The name match is a heuristic.

## The rule

> For writes, use true for potentially destructive or irreversible effects, such as deletion, overwriting, cancellation, access revocation, or irreversible sends or transactions.

Source: [OpenAI plugin guidelines, section 6.3](https://developers.openai.com/plugins/plugin-guidelines)

## How to fix it

Set "destructiveHint": true.

1. Set destructiveHint: true on every delete, remove, purge, overwrite, cancel, revoke and reset tool.
2. Do not set false because the action can be undone: OpenAI says reversibility does not justify it.
3. Consider a dry_run argument as well (see the delete-guard check).

Before:

```json
{ "name": "delete_issue", "annotations": { "readOnlyHint": false, "destructiveHint": false } }
```

After:

```json
{ "name": "delete_issue", "annotations": { "readOnlyHint": false, "destructiveHint": true } }
```

### TypeScript SDK

```ts
import { McpServer } from '@modelcontextprotocol/server';
import * as z from 'zod';

const server = new McpServer({ name: 'issues', version: '1.0.0' });

server.registerTool(
  'delete_issue',
  {
    title: 'Delete issue',
    description: 'Delete one issue permanently. Use only when the user explicitly asks to delete an issue.',
    inputSchema: z.strictObject({
      issue_id: z.string().describe('Issue ID, for example ISS-42'),
    }),
    annotations: { readOnlyHint: false, destructiveHint: true, openWorldHint: false },
  },
  async ({ issue_id }) => ({ content: [{ type: 'text', text: 'Done' }] }),
);
```

### Python SDK

```python
from typing import Annotated

from pydantic import Field
from fastmcp import FastMCP
from mcp.types import ToolAnnotations

server = FastMCP("issues")

@server.tool(
    title="Delete issue",
    annotations=ToolAnnotations(readOnlyHint=False, destructiveHint=True, openWorldHint=False),
)
def delete_issue(
    issue_id: Annotated[str, Field(description="Issue ID, for example ISS-42")],
) -> str:
    """Delete one issue permanently. Use only when the user explicitly asks to delete an issue."""
    return "Done"
```

## Questions

### Our delete goes to a trash bin. Is it still destructive?

Yes. OpenAI’s guidelines say the ability to undo does not justify destructiveHint: false for deletion, overwriting or cancellation.

### How does the checker know a tool deletes?

From its name (delete, remove, purge, overwrite, cancel, revoke, reset and similar). It is a heuristic; a false match can be ignored.

## Related checks

- [Every tool carries the applicable hint](https://isokron.ai/mcp-check/checks/anthropic-hint)
- [Delete tools take a confirm or dry-run argument](https://isokron.ai/mcp-check/checks/surface-delete-guard)
- [Tools named as writes are not marked read-only](https://isokron.ai/mcp-check/checks/annot-write-marked-readonly)
- [MCP tool annotations](https://isokron.ai/mcp-check/checks/annotations)

## Further reading

- [MWS-ANN: testing that hints match behavior](https://isokron.ai/mws#mws-ann-1)

Counts toward: Anthropic connector directory, OpenAI plugin directory.

Rubric: https://isokron.ai/mcp-check/rubric

Check your tool list: https://isokron.ai/mcp-check
