Server has 4 tools with basic schemas and descriptions, but significant quality gaps. Tool descriptions are minimal (10-50 chars, well below the 194-char baseline). Parameter descriptions are missing entirely, the schema shows property names but no descriptions for 'query', 'schema', or 'table'. No output schemas documented. No error handling guidance. execute_sql and analyze_table are WRITE operations but descriptions do not state this, violating the command-tool pattern. No input validation, no recovery guidance, no pagination support despite SQL tools potentially returning large result sets.

• Expand each tool description to 100-200 chars. For execute_sql: 'Execute a SQL query against the Hologres database. Returns query results as structured rows. Use get_query_plan() first to validate syntax. Modifies data if query contains INSERT/UPDATE/DELETE.'
• Add descriptions to every parameter. E.g., 'query' → 'SQL query string (SELECT, INSERT, UPDATE, DELETE, or DDL). Max 10000 chars. Validate syntax with get_query_plan() before executing.'
• Document output schemas for each tool. E.g., execute_sql returns {rows: [{col1: string, col2: number, ...}], rowCount: number, executionTime: number}.
• Add error handling guidance. E.g., 'If query fails with syntax error, call get_query_plan(query) to diagnose. If table not found, use analyze_table() to check table existence.'
• For WRITE operations, add confirmation pattern. E.g., 'This tool modifies data. Consider calling get_query_plan() first to preview the impact. Provide a dry_run parameter to preview changes without committing.'

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

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