Three tools with WRITE operations, but descriptions are mixed-language (Chinese/English), parameter descriptions lack specificity, and no output schemas are documented. All three tools are directly visible in src/index.ts with explicit registration. However, critical quality gaps prevent higher scores: descriptions are under 100 chars in some cases, parameter types are present but descriptions are vague (e.g., 'workspace dir' provides no context on format or constraints), and error handling is generic (McpError wrapping without actionable guidance). The bilingual description text creates ambiguity for English-speaking LLMs. No output schema documentation means agents cannot plan downstream operations. File write operations (WRITE risk) lack confirmation or dry-run patterns.

• Rewrite all descriptions in English only, 50-200 characters, starting with a verb. Example: 'generate_api_client' → 'Generate TypeScript API client and type definitions from a Swagger/OpenAPI spec file or URL. Writes output to {dir}/apis/. Requires absolute or relative file path starting with / or a full URL.'
• Add explicit parameter constraints for 'source': specify regex pattern (must start with / or http://, file extension must be .json), and valid URL schemes (http, https, or file paths).
• Add explicit parameter constraints for 'dir': document whether absolute/relative paths are accepted, whether directory must pre-exist, and confirm output directory structure.
• Document output schemas. Return JSON with typed fields: { type: 'object', properties: { output_path: { type: 'string', description: 'Path to generated files' }, files_written: { type: 'array', items: { type: 'string' }, description: 'List of created files' }, status: { type: 'string', enum: ['success', 'partial', 'failed'] } } }.
• Add tool annotations: mark all three as destructiveHint=true (file writes) and idempotentHint=false (to signal agents these operations may have side effects if retried).
• Implement a dry-run parameter or confirmation step for file writes. Either: (1) add 'dry_run: bool' parameter, or (2) return a confirmation request via MRTR pattern (result with input_required type) before writing files.
• Enhance error responses with actionable recovery guidance. Instead of 'Failed to generate API client', return: 'Failed to parse Swagger spec from {source}: {specific_parse_error}. Verify file is valid OpenAPI 3.0 or Swagger 2.0 JSON.'