GDB MCP server has basic tool definitions with schemas and descriptions present, but significant quality gaps limit production readiness. All 4 tools have descriptions (10-50 chars, mostly short) and input schemas with type definitions. However, descriptions lack depth, they state WHAT but not WHEN or WHY to use each tool, and lack error recovery guidance. Parameter descriptions are minimal (e.g., 'Session ID' for 'id' param). Output schemas are not documented, callers cannot predict response structure. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear write/read semantics. Error handling is absent from visible code; no guidance on retryability, user-fixable vs fatal errors, or recovery paths. Tool composition is reasonable (open/call/close/list_sessions form a coherent session lifecycle), but missing idempotency guarantees and confirmation patterns for destructive operations.

• Document output schemas for all tools. E.g., 'open' should return {type: 'ok', session_id: string, timeout: integer}. 'call' should return {type: 'ok'|'error', output: string, exit_code?: integer}. Include these in tool definitions or a separate schema reference.
• Expand tool descriptions to 80-150 chars with WHAT/WHEN/WHY. Example: 'open: Start a new GDB debugging session. Use this before calling any GDB commands. Returns a session_id required for all subsequent calls. Timeout defaults to 300s; increase for long-running debugs.'
• Add tool annotations: mark 'close' with destructiveHint=true, 'list_sessions' with readOnlyHint=true, 'call' with destructiveHint=true (since GDB commands can modify program state). This guides agent reasoning about side effects.
• Enhance parameter descriptions with format/constraint info. E.g., 'command: GDB CLI command string (e.g., "break main", "continue", "print x"). See GDB Commands Reference resource for valid commands. MI commands not supported in this version.'
• Implement error recovery guidance in tool responses. When 'call' fails, return {type: 'error', message: 'Session not found', recovery: 'Call list_sessions() to see active sessions, or open() to create a new one'}. This enables LLM self-correction.

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

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