This server has critical gaps in definition quality. While 4 tools are registered with basic schemas, the definitions are severely undermined by: (1) tool names that do not follow verb_noun conventions (configureProjectPaths, resetPathConfig are imperative but lack action clarity), (2) descriptions that are overly long (500+ chars) and written in Chinese with critical AI-specific instructions embedded ('【必须首先调用】'), creating confusion about agent vs. human intent, (3) parameters that lack detailed type constraints and validation guidance, (4) no visible error handling specifications or recovery guidance, (5) no documented output schemas for any tool, (6) no pagination or result limits documented despite potential for large dataset returns. The server is currently visible only as a partial source snippet; the full GeneratorTools.java implementation is truncated, meaning input schemas and handler code cannot be fully verified. Per the scoring rules, inferred or partially-visible tool definitions cap at 50; however, the severe quality issues below that threshold warrant a lower overall score.

• Rename tools to follow verb_noun convention with clear, lowercase naming: 'get_code_generation_guide', 'configure_project_paths', 'reset_project_paths', 'scan_project_structure'. This allows LLMs to parse intent from the name alone.
• Rewrite all descriptions in English, remove AI-specific instructions like '【必须首先调用】', and keep them to 50 - 200 characters. Example: 'getGenerationGuide' → 'Retrieve the step-by-step workflow for generating business code from database schema.'
• Document output schemas for each tool. Specify the return type (object, array, string) and all fields with types and descriptions. Example: 'Returns: {guide: string, steps: [{stepNumber: int, action: string, description: string}]}'.
• Add validation constraints to all parameters. For 'configureProjectPaths', specify: 'backendRootPath must be an absolute path (e.g., /home/user/project/src) or relative path from project root. Max 255 characters. Forward slashes only.'
• Add error handling guidance to each tool description or in a separate 'error cases' section. Example: 'If projectRoot does not exist, returns {success: false, error: "Directory not found", suggestion: "Check path and try again"}.'
• Provide the complete GeneratorTools.java source (not truncated) so tool implementations, exception handling, and return types can be verified.
• If certain tools must be called in a specific order (e.g., getGenerationGuide → configureProjectPaths → scanProjectStructure), document this as a workflow guide separate from tool descriptions, not embedded in the tool definition itself.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry