Single tool 'query' has a clear verb-noun name and basic schema with types. However, description is minimal (18 chars, below 20-char threshold), lacks context on when/why to use it, and omits critical safety guidance for a database tool. Parameters have types but descriptions are terse (8-15 chars each). No output schema documented. No error handling guidance. No mention of SQL injection risks or query limits. Tool lacks idempotency hints and destructive operation warnings despite accepting arbitrary SQL.

• Expand tool description to 50-150 chars: 'Execute SQL queries against CockroachDB. Returns structured results with row count, field metadata, and execution time. Use for read-only discovery; destructive operations require explicit confirmation.'
• Add parameter descriptions with constraints: database → 'Database name (alphanumeric, 1-63 chars). Must exist and be accessible.'; sql → 'SQL statement (SELECT, EXPLAIN ANALYZE only; no INSERT/UPDATE/DELETE without confirmation). Max 10,000 chars.'; explainAnalyze → 'When true, prefixes query with EXPLAIN ANALYZE to show execution plan. Useful for debugging slow queries.'
• Document output schema in tool description: 'Returns {rowCount: number, fields: [{name, dataTypeID}], rows: any[], command: string, duration: string}. For EXPLAIN ANALYZE, returns execution plan as text.'
• Add error handling guidance: 'If query fails, error message includes reason (syntax, timeout, permission). Syntax errors are not retryable; timeouts can be retried with LIMIT clause. For permission errors, verify database access.'
• Implement query safety: add max_rows parameter (default 100, max 10,000), query timeout (default 30s), and reject INSERT/UPDATE/DELETE unless explicitly allowed. Return clear error: 'Destructive operations not allowed. Use read-only queries only.'