Two tools with explicit schemas and descriptions. build_project has a comprehensive, well-structured input schema with 15+ optional parameters covering framework-specific configuration (Java version, Python version, database type, etc.). Descriptions are clear and present. list_frameworks is minimal but functional. However, critical gaps include: (1) no output schemas documented for either tool, forcing LLMs to guess what fields the response contains; (2) missing descriptions for several framework-specific nested parameters (javaVersion, pythonVersion, springBootVersion, database all lack type/constraint documentation in the schema); (3) projectType enum is present but appears decoupled from framework, no guidance on which projectType is valid for which framework; (4) no error handling or recovery guidance documented; (5) no idempotency, dry-run, or confirmation step for the destructive write operation build_project. The tool definitions are registered and visible in src/index.ts, not inferred. Parameter names follow verb_noun conventions adequately (build_project, list_frameworks), but output structure is completely undocumented.

• Document the output schema for build_project. Specify: Does it return a success flag? A file path? A list of created files? Status message? Include example: {success: boolean, projectPath: string, filesCreated: string[], output: string}
• Document the output schema for list_frameworks. Specify: Is it an array of strings? An object with categories? Include example: {frameworks: string[], categories: {[key: string]: string[]}}
• Add error recovery guidance to build_project description: 'If the framework is not recognized, call list_frameworks() first to see supported options. If the outputPath is invalid, return a clear error indicating the issue (e.g., directory not writable, path does not exist).'
• Add framework-to-projectType compatibility rules in the build_project description or as a separate validation tool. Document which frameworks are compatible with which projectTypes (e.g., spring-boot works with web/api only; react works with web only).
• Add idempotency documentation: 'If the output directory already exists, should the tool skip creation (idempotent) or fail? If skip, document the return value for a no-op case.'
• Enhance nested parameter descriptions with format and range constraints. E.g., javaVersion: 'Java version (11, 17, 21; default: 17)', pythonVersion: 'Python version (3.9, 3.10, 3.11, 3.12; default: 3.11)'
• Expand list_frameworks description to ~100 chars: 'List all supported frameworks available for project creation. Call this before build_project to verify framework names and avoid invalid requests. Returns a list of framework identifiers grouped by category (backend, frontend, etc.).'