Single tool 'mysql_query' with critical deficiencies. Input schema present but severely underdescribed: 'sql' parameter lacks format constraints, length limits, or usage guidance. Tool description is generic and does not explain WHEN to use it, what it returns, or how to handle destructive operations. No output schema documented. No error handling guidance. No parameter validation rules stated. Destructive operations (INSERT, UPDATE, DELETE, DDL) exposed without confirmation or dry-run pattern. Schema-specific permissions mentioned in description but not reflected in parameters or documented return structure.

• Add comprehensive output schema documenting return structure: success boolean, rows_affected (for mutations), result_set (for SELECT with column names and types), execution_time_ms, and error details if applicable.
• Expand 'sql' parameter description to: 'SQL query string (SELECT, INSERT, UPDATE, DELETE, or DDL). Max 10000 chars. Supports parameterized queries. Schema extracted from USE statement or defaults to MYSQL_DB env var. Mutations require appropriate ALLOW_*_OPERATION flag.'
• Implement confirmation pattern for destructive operations: add optional 'dry_run' boolean parameter (default false) that returns affected row count without executing, or require explicit 'confirm_destructive=true' for DELETE/DROP.
• Document error responses with actionable guidance: 'SQL syntax error at position X: [details]. Verify table/column names and use backticks for reserved words.' Include permission denial messages: 'DELETE not allowed on schema [schema]. Contact admin to enable ALLOW_DELETE_OPERATION.'
• Add tool annotations (destructiveHint, readOnlyHint, idempotentHint) to schema to signal operation safety to clients. Mark mysql_query with destructiveHint=true when query contains DELETE/DROP/TRUNCATE.

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

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