# Read-only tools set destructiveHint: false

**A tool with readOnlyHint: true should set destructiveHint: false: the specification ignores destructiveHint on read-only tools, but the pair contradicts itself and OpenAI asks for false.**

Check `openai-readonly-destructive` · OpenAI plugin directory · default severity: attention · rubric 2.1.0. Last verified against OpenAI plugin guidelines, section 6.3 on 2026-11-18.

## What fails

The tool sets both readOnlyHint: true and destructiveHint: true, which contradict each other. The specification ignores destructiveHint on read-only tools, but OpenAI asks for false.

## The rule

> destructiveHint: Use false for read-only tools.

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

## How to fix it

Set "destructiveHint": false, or set readOnlyHint to false if the tool does change data.

1. On read-only tools set destructiveHint: false.
2. If the tool does change data, set readOnlyHint: false instead and keep 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(
  'get_issue',
  {
    title: 'Get issue',
    description: 'Return one issue by ID. Use when the user names an issue.',
    inputSchema: z.strictObject({
      issue_id: z.string().describe('Issue ID, for example ISS-42'),
    }),
    annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
  },
  async ({ issue_id }) => ({ content: [{ type: 'text', text: 'Done' }] }),
);
```

### Python SDK

```python
from typing import Annotated

from pydantic import Field
from mcp.server.mcpserver import MCPServer
from mcp.types import ToolAnnotations

server = MCPServer("issues")

@server.tool(
    title="Get issue",
    annotations=ToolAnnotations(readOnlyHint=True, destructiveHint=False, openWorldHint=False),
)
def get_issue(
    issue_id: Annotated[str, Field(description="Issue ID, for example ISS-42")],
) -> str:
    """Return one issue by ID. Use when the user names an issue."""
    return "Done"
```

## Questions

### Which value wins in clients?

Per the specification, readOnlyHint: true makes destructiveHint meaningless. Reviewers still read the pair as an error in the annotations.

### Why would a server send both true?

Usually a default of destructiveHint: true applied to every tool, with readOnlyHint set per tool.

## Related checks

- [readOnlyHint, destructiveHint and openWorldHint are explicit booleans](https://isokron.ai/mcp-check/checks/openai-hints-explicit)
- [Every tool carries the applicable hint](https://isokron.ai/mcp-check/checks/anthropic-hint)
- [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)

Counts toward: OpenAI plugin directory.

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

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