MCP CV Server has significant gaps in definition quality. Tool naming follows verb patterns (get_, search_, query_, send_) which is good, but descriptions are universally too brief (under 50 chars) and lack LLM-optimization guidance. Input schemas are present for all tools but mostly lack parameter descriptions beyond the required 'query' and 'category' fields. Most critically, tools with empty input schemas (get_personal_info, get_work_experience, get_education, get_skills) lack any documentation of what they return or why an LLM should call them. Error handling is basic and does not guide recovery. No output schemas are documented. The send_email tool lacks any mention of side effects or irreversibility. Tool descriptions fail to explain WHEN to use each tool vs alternatives (e.g., search_cv vs query_cv distinction is unclear).

• Expand all four get_* tool descriptions to 50-200 characters explaining WHAT data they return and WHEN an LLM should call them (vs search_cv). Example: 'Retrieve all personal contact details from the CV (name, email, phone, location). Use this as a starting point when the user asks for contact info; use search_cv if they ask for a specific field.'
• Document output schemas for all tools. Add a comment in mcp-tools.js listing the response structure, e.g., 'Returns {success: bool, data: {...}, summary: string, [latest]: {...}, [count]: number}'. Include this in tool descriptions or a separate schema registry.
• Merge search_cv and query_cv into a single search_cv tool, or clearly distinguish: 'search_cv: Free-text keyword search across all CV fields. query_cv: Structured lookup by category with optional sub-query. Use query_cv when user specifies a category (education, skills, etc.); use search_cv for keyword matching.' Add enums or separate params to remove ambiguity.
• Add destructiveHint: true annotation (or explicit description clause) to send_email: 'Sends an email notification (irreversible). Calling this twice with the same parameters will send two emails.'
• Replace generic error messages with recovery guidance. Example: 'No education information available. Try calling search_cv with "education" or query_cv with category="education". If still empty, check that CV data was loaded during server initialization.'
• Add limits and pagination to search_cv. Update description: 'Search CV content for keywords. Returns up to 50 matching sections. Use limit parameter (1-100) to adjust. No pagination cursor needed; results are in-memory.' Add limit: {type: 'integer', minimum: 1, maximum: 100, default: 50} parameter.