14 tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Most tools have 1-4 parameters with type info, but descriptions are minimal (10-50 chars). No tool annotations (readOnlyHint/destructiveHint). Error handling and recovery guidance absent. Naming is verb-forward (get_, execute_, add_) but some descriptions lack context on when to use each tool vs. alternatives (e.g., execute_reader vs. execute_nonquery distinction unclear). Output schemas not documented, LLMs cannot plan downstream calls. No pagination guidance for potentially large result sets (get_tables, get_routines).

• Add output schemas to all tools. Document field names, types, and what each field represents. E.g., get_tables should return [{table_name: string, schema: string, row_count: int}].
• Expand descriptions to 100-200 chars. Include WHEN to use (e.g., 'Use execute_reader for SELECT queries; use execute_nonquery for INSERT/UPDATE/DELETE'). Add prerequisites (e.g., 'Call get_tables first to discover available tables').
• Add tool annotations: mark get_* tools with readOnlyHint=true; mark execute_nonquery, execute_routine, add_row with destructiveHint=true; mark idempotent operations with idempotentHint=true.
• Implement pagination for list tools. Add limit (default 20, max 100) and offset/cursor parameters. Return total_count so LLMs know if more results exist.
• Add error recovery guidance. E.g., execute_reader errors should suggest 'Check table/column names with get_tables or get_columns. Verify SQL syntax (SELECT only).' Categorize errors as retryable vs. user-fixable.