23 tools with explicit schemas and descriptions, but significant quality gaps. Tool names are action-oriented (open_, attach, execute, etc.) following verb_noun convention. However, descriptions are inconsistent: some are 10-15 chars (e.g., 'Attach debugger to a running process' is adequate at 42 chars), but many lack context on WHEN to use them or what they return. Parameter descriptions exist but are minimal (e.g., 'Session ID' with no guidance on format or origin). Output schemas are not documented, LLMs cannot predict what fields to expect from tools like analyze, stack_trace, or read_memory. Error handling is absent from descriptions. No guidance on idempotency, retryability, or side effects. The write_memory tool (DESTRUCTIVE risk) lacks a confirmation pattern or dry-run option. Script-related tools (load_script, run_script, invoke_script, eval_script) have overlapping responsibilities and unclear composition. Session management is implicit (session_id parameter everywhere) but never explained, how do sessions persist? Are they per-process? Per-connection? This forces LLMs to guess.

• Document output schemas for all tools. For example, stack_trace should specify: returns {frames: [{address, symbol, file, line}], thread_id, total_frames}. This enables LLMs to chain tools correctly.
• Add session lifecycle documentation. Explain in tool descriptions: 'session_id is obtained from open_dump or attach. Sessions persist for the connection lifetime. Use execute to run arbitrary debugger commands within a session.'
• Add confirmation pattern to write_memory. Implement a dry_run parameter or a separate preview_write tool that shows what would be written before committing. Include idempotency guidance.
• Clarify script tool composition. Document: load_script prepares a script; run_script executes it top-to-bottom; invoke_script calls a specific function; eval_script evaluates inline code. Provide examples of when each is appropriate.
• Enhance parameter descriptions with format and range constraints. E.g., 'address: hex string (0x...) or symbol name (e.g., kernel32!CreateFileA). If omitted, uses current instruction pointer.' Add min/max for numeric params like max_frames (1-1000).

Inferred effective spec: 2026-07-28+.

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