Server has 6 tools with basic schemas and descriptions, but significant quality gaps. Tool names lack clear verb-noun structure (execute_dml_ddl_dcl_tcl is 24 chars and combines multiple operations). Descriptions are present but generic, many under 100 chars and lack WHEN/WHY context. Parameters have types but descriptions are minimal (e.g., 'transaction_id' param: 'The ID of the transaction to commit' is only 40 chars, lacks format guidance). No output schemas documented. Error handling returns JSON but lacks recovery guidance. Tool descriptions are in Chinese, reducing LLM clarity. No parameter constraints (enums, ranges, patterns). Critical issue: execute_dml_ddl_dcl_tcl auto-commits after execution, contradicting its description claiming it wraps in a transaction for user review, this is a dangerous semantic mismatch.

• Rename 'execute_dml_ddl_dcl_tcl' to 'execute_write_statement' or split into separate tools (execute_insert, execute_update, execute_delete, execute_create_table, etc.) to clarify intent.
• Translate all tool and parameter descriptions to English. Use clear, concise language: 'Execute a read-only SQL SELECT query. Returns rows and execution time.' (not Chinese descriptions).
• Document output schemas for all tools. Add a 'returns' section to each tool definition specifying field names, types, and meanings. E.g., execute_query returns {status: string, rows: array, execution_time_ms: number}.
• Fix execute_dml_ddl_dcl_tcl to actually implement the described behavior: BEGIN transaction, execute statement, PAUSE and return transaction_id to user, wait for user confirmation via execute_commit or execute_rollback. Remove auto-commit.
• Add parameter constraints: declare 'sql' as a string with minLength 5, maxLength 10000; add enum for transaction_id format; add description to each param explaining valid values, format, and examples.