Single tool 'check_my_architecture' has a Zod schema with all parameters optional and described, but critical issues undermine quality. Description is in Portuguese and lacks clarity on when/why to use the tool. Parameter descriptions are present but vague (e.g., 'Codigo opcional' instead of explaining what source code format is expected). No output schema is documented, the tool returns ArchitectureAnalysisResponse interface but this is not exposed to the LLM. Error handling returns generic error messages without recovery guidance. The tool combines multiple concerns (file reading, backend API call, optional auto-fix with file writes) in one operation, violating single-responsibility principle. No input validation or constraint documentation (e.g., file path traversal protection is implemented but not documented for the LLM). Tool name 'check_my_architecture' lacks a clear action verb and is ambiguous about what 'check' means.

• Translate tool description to English and expand to 100-200 characters explaining: (1) what the tool does (analyzes code architecture for SOLID violations and design patterns), (2) when to use it (when reviewing code quality or planning refactoring), (3) what it returns (analysis report with violations, suggestions, and optional refactored code).
• Document the output schema explicitly in the tool definition. Include field names, types, and descriptions for: analysis (string), violations (array of strings), suggestions (array of strings), patterns (array of strings), confidence (number 0-1), refactoredCode (optional string), architectureDiagram (optional string), metadata (optional object).
• Split the tool into two: (1) analyze_architecture (read-only, no auto_fix parameter) and (2) apply_architecture_fix (write operation, takes analysis result and applies refactoring). This enables agents to review before modifying and respects the command-tool pattern.
• Add parameter constraints and validation hints: file_path must be relative to workspace root or absolute within workspace; source_code must be valid code (not empty); llm_model must be a valid OpenRouter model identifier; auto_fix defaults to false to prevent accidental modifications.
• Enhance error messages with recovery guidance. E.g., 'Backend service unavailable (timeout after 30s). Retry in 10 seconds or check BACKEND_URL environment variable.' or 'Neither file_path nor source_code provided. Supply one of: file_path (string, relative or absolute path) or source_code (string, code content).'

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

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