This server has 23 tools with significant definition gaps. Most tools lack proper input schemas (cannot verify JSON Schema structure in source), descriptions are present but often generic or under-specified, and parameter types are not consistently documented. Tools like 'bootstrap', 'cleanup-branch', and 'migrate-state' have destructive/write side effects but lack confirmation patterns or dry-run guidance in descriptions. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are visible. Error handling is not documented. Output schemas are not specified. The server reads as a CLI wrapper rather than an LLM-optimized tool interface.

• Add explicit JSON Schema definitions with type, enum, and constraint declarations for all parameters. E.g., 'dry-run' should be {type: 'boolean'}, 'path' should be {type: 'string', description: 'Absolute or relative repository path'}.
• Wrap destructive tools (cleanup-branch, clear-wip, migrate-state) with a confirmation pattern: require a --confirm flag or return a 'confirmation_required' response with a summary of what would be deleted, forcing the LLM to call again with explicit approval.
• Add tool annotations to the MCP tool registration: mark 'context-summary', 'memory list', 'memory status' with readOnlyHint=true; mark 'cleanup-branch', 'clear-wip', 'migrate-state' with destructiveHint=true; mark 'memory store' with idempotentHint=true if repeated calls with same key/value are safe.
• Document output schemas for all tools. E.g., 'context-summary returns {stale: boolean, generated_at: ISO8601 string, summary_path: string, summary_content: string}'. Include this in tool descriptions or a separate schema field.
• Add error recovery guidance to tool descriptions. E.g., 'If bootstrap fails with "git not found", ensure git is installed and in PATH. If it fails with "permission denied", check directory ownership and run with appropriate permissions.'