Context7 MCP server provides 2 tools with reasonable naming conventions and clear descriptions. Both tools follow verb_noun patterns (query-docs, resolve-library-id) and include parameter descriptions. However, output schemas are not documented in the provided source, parameter validation constraints are minimal, and error handling guidance is absent. The server targets a specialized use case (documentation lookup) with read-only operations, which mitigates some risk but limits overall capability maturity.

• Document output schemas as JSON Schema objects in tool definitions. For query-docs, define: {type: 'object', properties: {snippets: {type: 'array', items: {type: 'object', properties: {code: {type: 'string'}, explanation: {type: 'string'}, ...}}}, ...}. For resolve-library-id, define: {type: 'array', items: {type: 'object', properties: {libraryId: {type: 'string'}, name: {type: 'string'}, description: {type: 'string'}, ...}}}.
• Add JSON Schema constraints to input parameters. For libraryId, use pattern: '^/[a-zA-Z0-9_-]+/[a-zA-Z0-9_-]+(/[a-zA-Z0-9_.-]+)?$'. For query and search text, set maxLength (e.g., 1000).
• Add error recovery guidance to both tool descriptions. Example: 'If no matching libraries are found, try a shorter or more generic query term.' 'If libraryId format is invalid, call resolve-library-id first to discover valid IDs.'
• Update query-docs description to reference the resolve-library-id dependency explicitly: 'Call resolve-library-id(query) first if you don't have a libraryId. This tool requires a valid Context7-compatible libraryId in format /org/project or /org/project/version.'
• Expand parameter descriptions with validation rules and examples (without including literal example values for LLMs to copy). E.g., 'Package or library name: Enter the full name (e.g., react, lodash) or a partial name. Supports typo tolerance.' 'User query: Plain English question about the library (max 500 chars); may include version or feature-specific context.'