Server provides 15 tools with consistent naming (verb_noun pattern) and reasonable descriptions (avg ~80 chars). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not documented in the source code, parameter constraints lack enums/ranges, and error handling guidance is minimal. Security-sensitive tools (delete_file, run_command) lack confirmation patterns. No tool annotations (readOnlyHint, destructiveHint) visible despite risk classifications in metadata.

• Document output schemas for all tools. Specify return types, field names, and structure. Example: list_files returns {files: [{name: string, path: string, is_dir: boolean, size: integer}], total: integer}.
• Add tool annotations via ToolAnnotations type: mark delete_file, write_file, append_file, move_file with destructiveHint=true; mark read_file, list_files, git_status with readOnlyHint=true; mark idempotent operations with idempotentHint=true.
• Implement confirmation pattern for delete_file and run_command. Add a 'dry_run' parameter or require explicit confirmation via a separate confirm_operation tool before executing irreversible actions.
• Add parameter constraints: git_log max_commits should have min=1, max=1000; run_command should document allowed commands and reject unlisted ones with clear error message listing available options.
• Enhance error messages with recovery guidance. Example: 'File not found at /path/to/file. Verify path is relative to workspace root. Call list_files() to explore available files.' instead of bare 404.

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

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)