The server provides 4 read-only database tools with clear naming (list_*, describe_*, execute_*) that follow verb-noun patterns. All tools have descriptions and basic input schemas. However, parameter descriptions are minimal or missing (e.g., 'database' parameter in list_tables has only 'Database name (optional, uses default if not specified)', lacks specificity on what 'default' means). No output schemas are documented. Error handling is absent, no guidance on what happens if a database doesn't exist, if a query fails, or how to recover. The descriptions are functional but terse (avg 52 chars), below the 194-char production baseline. Tool names are excellent (list_databases, execute_query), but parameter documentation falls short of the 72-char average and lacks actionable constraint information.

• Document output schemas for all four tools. Specify what fields are returned. E.g., list_databases should return {databases: [{name: string, charset: string, ...}]}. describe_table should return {columns: [{name, type, nullable, key, ...}]}. This enables agents to plan downstream actions.
• Expand parameter descriptions to 70+ characters with actionable constraints. For 'database' param: 'The database name (string, case-sensitive, required if not using default). Default: value of MYSQL_DATABASE env var. If database does not exist, tool returns error.' For 'table' param: 'The table name (case-sensitive). Can use schema-qualified names (schema.table) or bare names if using current database.'
• Add explicit error guidance to tool descriptions. E.g., execute_query: 'Allowed statements: SELECT, SHOW, DESCRIBE, EXPLAIN. Disallowed: INSERT, UPDATE, DELETE, DROP, CREATE. If query fails, returns error with SQL error code and message. If query times out after 30s, returns timeout error.'
• Clarify result limits. Add to list_databases/list_tables: 'Returns max 100 items. If more exist, response includes next_cursor for pagination.' to prevent context explosion.
• Document the read-only guarantee explicitly in tool descriptions. E.g., 'This tool executes read-only SQL queries only. Write operations (INSERT, UPDATE, DELETE, etc.) are rejected and return a permission error.'
• Add parameter examples in schema (not description). Use JSON Schema 'examples' field: 'database': {type: 'string', description: '...', examples: ['customers', 'orders']}. This guides LLMs without polluting the description text.

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

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