Three tools with clear verb-noun naming (list_tables, describe_table, run_query) and good descriptions (100-150 chars each). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not formally documented, responses are returned as strings (JSON or formatted text) without explicit schema declarations. Error handling returns formatted error messages but lacks recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite all three being read-only. Parameter descriptions are adequate but could be more prescriptive about constraints (e.g., SQL validation rules for run_query).

• Add explicit output schema documentation to each tool. Define the structure of returned JSON (e.g., describe_table returns array of {column_name, data_type, nullable, primary_key}; list_tables returns array of {table_name, type}).
• Annotate all three tools with readOnlyHint=true and idempotentHint=true in the tool definition to signal safety and retry semantics to agents.
• Enhance run_query error messages with recovery guidance: 'SQL validation failed: only SELECT and WITH statements allowed. Received: <statement_type>. Retry with a valid read-only query.'
• Add optional limit and offset parameters to list_tables and run_query to support pagination. Return a total_count field so agents can iterate through large result sets.
• Document SQL validation rules explicitly in run_query description: 'Validates that SQL contains only SELECT or WITH keywords. Rejects INSERT, UPDATE, DELETE, DROP, CREATE, ALTER, and other write operations.'

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

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