Server has 7 tools with complete input schemas and descriptions. Naming follows verb_noun convention (prepare_, start_, execute_, get_, close_). Descriptions are present but brief (avg 60 chars, below 194-char baseline). Parameters are typed and described, but lack constraints (enums, ranges, patterns). Output schemas are not documented in the visible code. Error handling exists but recovery guidance is minimal. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications in metadata.

• Document output schemas for all 7 tools. Specify field names, types, and whether results are paginated. Example: execute_windbg_command returns {status: 'success'|'timeout'|'error', output: string, error_message?: string}.
• Expand tool descriptions to 100-200 chars. Add WHEN to use (e.g., 'Call after start_analysis_session to run debugger commands') and any prerequisites or dependencies.
• Add tool annotations: mark execute_windbg_command and async variants with readOnlyHint=true; mark prepare_dump_upload, start_analysis_session, close_analysis_session with destructiveHint=true.
• Add parameter constraints: timeout should have minimum=1, maximum=3600; command should document expected CDB syntax or link to CDB reference; file_size should have minimum=1.
• Enhance error responses with recovery guidance. Example: 'Session not found (session_id=xyz). Call start_analysis_session() first to create a session.' instead of bare error codes.

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

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