Scoring was not performed

• Create formal MCP tool definitions with complete JSON Schema input and output specifications. Move away from Vue composable-based tool definition to explicit MCP server tool registration.
• Add comprehensive English descriptions (50-150 characters) for each tool explaining WHAT it does, WHEN to use it, and WHAT it returns. Example: 'List all documentation pages with their paths and metadata. Use this first to discover available pages before calling get-page. Returns array of {path, title, lastModified}.'
• Document all input parameters with type, format, and constraints. For 'path': specify if it is a string path like 'docs/intro' or '/guide/setup', whether it is required or optional, and valid path patterns. For 'exampleName': specify exact matching vs partial match, case sensitivity, and available example names.
• Define and document output schemas for each tool. E.g., list-pages returns [{path: string, title: string, lastModified?: ISO8601}], get-page returns {path, content, metadata}. This enables LLM planning and proper result chaining.
• Add error handling and recovery guidance. Document what happens if path is not found, what to do if the user provides a partial or misspelled example name (suggest alternatives), and when to retry vs ask the user for clarification.
• Provide pagination support for list tools. If there are many pages or examples, add limit/offset/cursor parameters to list-pages and list-examples, and document the response structure with totalCount and nextCursor.
• Add parameter dependencies documentation. If any parameter's validity depends on another, state this clearly. Example: 'If path does not include a file extension, assumes .md; if extension is provided, respects it.'