mysql-mcp has well-structured tool definitions with clear naming (verb_noun pattern: mysql_query, mysql_execute, etc.) and comprehensive descriptions in Chinese. All 8 tools have input schemas with type definitions. However, parameter descriptions are minimal (often just the SQL statement or table name), and output schemas are not documented. Error handling exists but lacks recovery guidance. Security checks (SQL injection prevention, permission gates) are present but not reflected in tool annotations. The server caps results at MAX_ROWS (1000) but does not document pagination or result limits in tool descriptions.

• Document output schemas for all tools. E.g., mysql_query returns array of objects with column names as keys; mysql_list_tables returns {table_name, engine, estimated_rows, total_size, ...}. Use JSON Schema or explicit field descriptions.
• Enhance parameter descriptions with constraints. E.g., 'sql: SQL SELECT statement (max 4096 chars, supports SELECT/WITH/EXPLAIN/SHOW/DESCRIBE only)' and 'table: Table name (alphanumeric + underscore, case-sensitive)'.
• Add tool annotations: mark mysql_query, mysql_list_tables, mysql_describe_table, mysql_show_indexes, mysql_show_create_table, mysql_explain, mysql_list_databases with readOnlyHint=true; mark mysql_execute with destructiveHint=true.
• Improve error messages with recovery guidance. E.g., 'SQL contains DROP statement (line 1). Allowed: SELECT, WITH, EXPLAIN, SHOW, DESCRIBE. Rewrite and retry.' For permission errors: 'INSERT not authorized. Set ALLOW_INSERT_OPERATION=true in env and restart.'
• Document result limits in descriptions. E.g., 'Returns up to 1000 rows. For larger datasets, use LIMIT/OFFSET in your SQL query.' Add optional limit/offset parameters to mysql_query for explicit pagination control.