# Every tool has a title

**Every tool needs a short human-readable title, such as "Create issue", for the Claude connector directory; either the top-level title field or annotations.title counts.**

Check `anthropic-title` · Anthropic connector directory · default severity: blocking · rubric 2.1.0. Last verified against Anthropic connector pre-submission checklist on 2026-11-18.

## What fails

The title is the name people see in Claude. Either the top-level "title" or "annotations.title" counts.

## The rule

> Every tool must include a `title` and the applicable hint: `readOnlyHint: true` for read-only tools, and `destructiveHint: true` for tools that modify or delete data.

Source: [Anthropic connector pre-submission checklist](https://claude.com/docs/connectors/building/review-criteria#provide-tool-annotations)

## How to fix it

Add a short, human-readable "title", for example "Create issue".

1. Add a title to every tool: a few words, sentence case, no underscores.
2. Use the top-level title field (both SDKs take it as an option).
3. Keep the machine name in name, the human name in title.

Before:

```json
{ "name": "create_issue", ... }
```

After:

```json
{ "name": "create_issue", "title": "Create issue", ... }
```

### 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(
  'create_issue',
  {
    title: 'Create issue',
    description: 'Create one issue in a project. Use when the user asks to file or report something.',
    inputSchema: z.strictObject({
      project_id: z.string().describe('Project ID, for example PRJ-7'),
      title: z.string().describe('Issue title, one line'),
    }),
    annotations: { readOnlyHint: false, destructiveHint: false, openWorldHint: false },
  },
  async ({ project_id, title }) => ({ 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="Create issue",
    annotations=ToolAnnotations(readOnlyHint=False, destructiveHint=False, openWorldHint=False),
)
def create_issue(
    project_id: Annotated[str, Field(description="Project ID, for example PRJ-7")],
    title: Annotated[str, Field(description="Issue title, one line")],
) -> str:
    """Create one issue in a project. Use when the user asks to file or report something."""
    return "Done"
```

## Questions

### Top-level title or annotations.title?

Both are in the specification and both satisfy the checklist. Prefer the top-level title, which current SDKs set and clients read first.

### Where does the title appear?

In client UIs: tool lists, permission prompts and call logs. The model mostly reads the name and description.

## Related checks

- [Every tool carries the applicable hint](https://isokron.ai/mcp-check/checks/anthropic-hint)
- [readOnlyHint, destructiveHint and openWorldHint are explicit booleans](https://isokron.ai/mcp-check/checks/openai-hints-explicit)
- [Tool names that say what the tool does](https://isokron.ai/mcp-check/checks/openai-name-opaque)
- [MCP tool annotations](https://isokron.ai/mcp-check/checks/annotations)

Counts toward: Anthropic connector directory.

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

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