ngmcp defines 9 tools with consistent naming (verb_noun pattern: get_, list_, read_, follow_, search_) and clear descriptions (avg ~100 chars). All tools are READ_ONLY and well-scoped. However, parameter descriptions are minimal (often just 'Absolute path to the .ng file'), and output schemas are not documented in the visible code. The server lacks error handling guidance, recovery hints, and structured output documentation. Tool composition is sound (each does one thing), but descriptions could be more LLM-optimized per the 50-200 char baseline.

• Document output schemas for all tools. Specify field names, types, and structure. E.g., list_entries returns [{offset: int, title: string, ...}]. This enables LLMs to chain tools correctly.
• Expand parameter descriptions to 50-100 chars. Include format constraints, valid ranges, and error cases. E.g., 'Absolute path to a .ng file (must exist and be readable; relative paths not supported).'
• Add error handling guidance to tool descriptions. E.g., 'Returns error if file not found; try list_guide_files() to discover available guides.'
• Document pagination and result limits. If list_entries or search tools cap results at N items, state this and explain how to paginate or refine queries.
• Clarify tool selection hints. E.g., 'Use line_search_guide to find entries where a query appears on a single line; use body_search_guide for multi-line matches.'