Server has 10 tools with basic schemas and descriptions, but significant quality gaps. Tool names lack consistent verb-noun structure (e.g., 'leer_archivo' vs 'listar_archivos' mixing Spanish/English conventions). Descriptions are present but generic (avg ~80 chars, below 194-char baseline). Parameter descriptions exist but lack constraints, ranges, and format specifications. No output schemas documented. Error handling returns raw exception strings rather than actionable recovery guidance. One tool (ejecutar_comando) is destructive but lacks confirmation/dry-run pattern. No tool annotations (readOnlyHint/destructiveHint) despite MCP support.

• Add explicit output schemas to all tools. Document return type, field names, and structure. Example: 'Returns {"models": [string], "total": int}' for list_models.
• Implement confirmation/dry-run pattern for 'ejecutar_comando'. Add a 'dry_run' boolean parameter and require explicit confirmation before executing shell commands. Log all executions with timestamp and user context.
• Replace raw exception strings with actionable error messages. Example: 'File not found at src/main.py. Check path spelling or call listar_archivos(".") to discover available files.' Include error classification (retryable/user-fixable/fatal).
• Add JSON Schema constraints to parameters. Use 'minimum', 'maximum', 'pattern', 'enum' fields. Example: temperature with minimum=0.0, maximum=2.0. Add path validation to 'ruta' to prevent directory traversal.
• Standardize naming to English verb_noun format. Rename: 'leer_archivo' → 'read_file', 'listar_archivos' → 'list_files', 'revisar_codigo' → 'review_code', 'generar_tests' → 'generate_tests', 'documentar_codigo' → 'document_code', 'sugerir_commit' → 'suggest_commit_message'.