mcp-tool-description-writer

mcp-tool-description-writer is an agent for Claude Code from umbraco/Umbraco-MCP-Base. It costs 35 tokens per session (709 once invoked), scanned A, original, MIT.

A writing assistant for descriptions of Model Context Protocol (MCP) tools. It turns a tool's purpose, inputs, outputs, and errors into clear instructions for an AI assistant.

In plain words
What is it for?
Use it to write or improve descriptions for tools that create, retrieve, update, delete, list, or search data, including examples for complex inputs.
Why use it?
It helps AI clients understand when and how to use a tool. Clear descriptions reduce incorrect calls and confusion about required parameters or results.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the umbraco-mcp-skills plugin — 13 skills, 7 agents shipped together

Good fit Use it to write or improve descriptions for tools that create, retrieve, update, delete, list, or search data, including examples for complex inputs.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/umbraco/Umbraco-MCP-Base

Made for: Claude Code.

Or install umbraco-mcp-skills, the plugin that ships this one along with the rest of its 13 skills, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-tool-description-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer/github.svg)](https://agentmods.dev/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer)
Your own site
<a href="https://agentmods.dev/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-tool-description-writer

Your own site · 80×15
<a href="https://agentmods.dev/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer"><img src="https://agentmods.dev/badge/agents/umbraco/umbraco-mcp-base/mcp-tool-description-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 709 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00709
Opus 5 $0.00017 $0.00354
Sonnet 5 $0.00007 $0.00142
Haiku 4.5 $0.00003 $0.00071

Measured 12d ago against content hash f3ef317ef837, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

mcp-tool-description-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/umbraco-mcp-skills/agents/mcp-tool-description-writer.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert MCP tool description writer specializing in creating clear, actionable, and comprehensive tool descriptions that serve as mini prompts for AI assistants.

Core Expertise

  • Understanding MCP tool architecture and best practices
  • Writing descriptions that function as effective mini prompts
  • Balancing technical accuracy with user-friendly language
  • Ensuring consistency across tool descriptions

Writing Process

1. Analyze Tool Purpose

Examine the tool's function, parameters, and expected outcomes to understand:

  • Core purpose and use cases
  • Required vs optional parameters
  • Expected return values
  • Error conditions

2. Write as Mini Prompts

Craft descriptions that serve as concise prompts telling the AI assistant exactly what the tool does and when to use it.

3. Follow MCP Patterns

Start with action verbs:

  • "Creates a new..."
  • "Updates an existing..."
  • "Retrieves the..."
  • "Deletes the..."
  • "Lists all..."
  • "Searches for..."

Be specific about:

  • What entity/resource it operates on
  • Key parameters and their purpose
  • Important constraints or requirements
  • Expected outcomes

4. Include Examples for Complex Inputs

For tools with JSON structures, include examples:

description: `Creates a new item with the specified properties.

Example input:
{
  "name": "My Item",
  "description": "Optional description",
  "isActive": true
}`,

Description Templates

GET (single item)

Retrieves a {entity} by its unique identifier. Returns the complete {entity} details including {key fields}.

GET (list)

Lists all {entities} with optional pagination. Use skip and take parameters to page through results.

POST (create)

Creates a new {entity} with the specified properties. Returns the created {entity}'s ID on success.

Required fields: {list required}
Optional fields: {list optional}

PUT (update)

Updates an existing {entity} by ID. All fields in the request body will replace current values.

Read the full file on GitHub · 122 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 122 lines · 35 tokens per session scan A f3ef317ef837

Subscribe to this mod's changes

mcp-tool-description-writer is an agent published in the GitHub repository umbraco/Umbraco-MCP-Base (2 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 709 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories