MCP Tool Description Economy

Standardize MCP tool descriptions by applying a fixed structure with a purpose verb, routing signal, cross-references, and a 10–16 word target length to ensure concise, scannable communication across teams.

The target length for an MCP tool description is 10–16 words. This constraint ensures descriptions remain scannable and concise while fitting the standardized YAML frontmatter structure.

Prevent leaking implementation details in MCP tool descriptions by applying the provided quality checklist, which verifies that parameter names and internal logic are excluded from the final routing and purpose text.

You need a standardized MCP tool description format during documentation workflows, PR reviews, and onboarding to ensure tool descriptions are cross-referenced, scannable, and consistent across teams.

Yes, you can use MCP tool description standardization for onboarding. It enforces a fixed structure with clear routing signals and cross-references, making tool capabilities easier for new team members to scan and understand.

YAML frontmatter for an MCP tool description should include a name and description, conforming to a fixed structure that enforces purpose, routing, cross-references, and target length constraints.