Three tools with clear verb-noun naming (execute_query, get_tables, get_columns) and basic parameter schemas. Descriptions are present but generic (10-50 chars). All tools have input schemas with types and descriptions, meeting baseline requirements. However, output schemas are not documented in tool definitions, only visible in implementation code. Parameter descriptions lack actionable constraints (e.g., no enum for schema parameter, no format guidance for query). Error handling exists in code but not surfaced in tool definitions. Security validation (SELECT-only check) is implemented but not declared in tool metadata.

• Document output schemas for each tool in the tool definition. Example for execute_query: 'Returns {columns: [string], rows: [[any]], row_count: int, has_more: bool}'. This enables LLMs to chain tools and extract correct fields.
• Expand parameter descriptions with constraints and examples. For query: 'SQL SELECT query (only SELECT allowed; max 10000 chars; no INSERT/UPDATE/DELETE)'. For schema: 'Schema name (optional; if omitted, uses default schema; e.g., "public" for PostgreSQL)'.
• Add tool annotations (readOnlyHint=true, idempotentHint=true) to all three tools. This signals to agents that these tools are safe to retry and do not modify state.
• Extend tool descriptions to 100-150 chars. Example: 'Execute a SELECT query against the connected database and return results. Use this to fetch data; call get_tables() first to discover available tables. Max 100 rows per call; use pagination for larger result sets.'
• Document error scenarios in tool descriptions. Example: 'Errors: connection_failed (retry with exponential backoff), invalid_query (check syntax), timeout (increase max_rows limit or simplify query)'.

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

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