Server has 6 tools with basic schemas and descriptions, but significant gaps prevent higher scores. All tools have descriptions (10-80 chars, mostly adequate) and input schemas using Zod, but parameter descriptions are sparse or missing. The query tool lacks critical safety documentation (SQL injection risk, parameterization guidance). Output schemas are not documented, LLMs cannot predict response structure. Error handling is absent from visible code. No tool annotations (readOnlyHint/destructiveHint) despite clear risk distinctions (5 READ_ONLY, 1 WRITE). Naming is verb-forward and clear (query, list_tables, describe_table, execute_migration, get_schema, list_databases), meeting baseline conventions. However, parameter-level documentation is weak: 'sql' param in query tool has no guidance on parameterization, injection prevention, or expected format.

• Add detailed parameter descriptions to query and execute_migration tools. Example: 'sql: SQL query string. Use parameterized queries with ? or $1 placeholders; pass values in params array to prevent SQL injection.'
• Document output schemas for all tools. Example for query: 'Returns array of objects where keys are column names and values are typed results. Example: [{id: 1, name: "users"}]'
• Add tool annotations via MCP SDK: readOnlyHint=true for query/list_tables/describe_table/list_databases/get_schema; destructiveHint=true for execute_migration.
• Implement dry-run or confirmation flow for execute_migration. Add optional 'dry_run' boolean parameter; return parsed statements and validation errors before execution.
• Add error recovery guidance in tool descriptions. Example: 'If table not found, call list_tables() first to verify table name and schema.'