Single tool 'query' has a basic description and minimal schema. The tool name lacks a verb prefix (should be 'execute_query' or 'run_query'), violating naming conventions. Input schema defines only 'sql' as a string with a short description. No output schema is documented, LLMs cannot predict the structure of returned rows. Error handling returns text responses rather than structured error objects with recovery guidance. The tool lacks parameter constraints (e.g., query length limits, timeout hints) and does not document what fields are returned or how pagination works for large result sets.

• Rename tool from 'query' to 'execute_query' to follow verb_noun convention and signal read-only intent clearly.
• Expand parameter description to 80 - 150 characters: 'SQL SELECT query to execute against the database. Max 5000 characters. Queries run in READ ONLY transaction. Returns array of objects with column names as keys.'
• Document output schema explicitly: 'Returns {rows: Array<Record<string, any>>, rowCount: number}. Each row is an object mapping column names to values.'
• Add limit and offset parameters (both optional, defaults: limit=100, offset=0) to prevent context window exhaustion and enable pagination.
• Enhance error messages with recovery hints: 'Syntax error in SQL: ... (Check column names and table names exist. Call list_tables resource first if unsure.)'.