45 tools with highly inconsistent definition quality. Only 8 tools have visible descriptions in source (codex_run, git_diff, git_status, read_file, search_text, shell, system_info, web_fetch, workspace_list, write_file, replace_in_file). 37 tools have NO descriptions visible, only names in tool-contract.js. Most tools lack visible input schemas; only ~11 have documented parameters. Python reference implementation shows good patterns (ToolAnnotations, path validation, output truncation) but TypeScript server definition is opaque. Average tool description length for documented tools: ~120 chars (below 194-char baseline). No output schemas documented. Error handling present in Python reference but unclear in main server.

• Add explicit descriptions to all 37 undocumented tools. Each must answer: What does it do? When to use it? What does it return? Target 50-200 chars per pattern:tool-description baseline.
• Document input schemas for all tools in source code. Use JSON Schema with explicit types (string, integer, boolean, enum) and descriptions for every parameter. Reference: pattern:constrained-input.
• Document output schemas. For each tool, specify the structure of the response (fields, types, pagination if applicable). This enables LLMs to plan tool chains and extract data correctly.
• Add confirmation/dry-run support for destructive tools (write_file, replace_in_file, shell, git_run, apply_patch). Implement pattern:confirmation-request to prevent accidental data loss.
• Expose tool definitions in source code (src/server.js or similar) rather than inferring from tool-contract.js. Show explicit tool registration with name, description, input schema, and output schema for all 45 tools.