Server exposes 5 tools with basic descriptions but significant quality gaps. All tools have descriptions (10-200 chars, within baseline range), but input schemas are minimal or absent. Tool names follow verb_noun pattern (ngfx_*) but lack clarity on distinctions. No parameter descriptions visible in schema definitions. No output schemas documented. Error handling and recovery guidance absent. Naming is domain-specific but could be clearer for LLM disambiguation (e.g., ngfx_deep_capture_capability_report vs ngfx_capture_capability_report).

• Document output schema for each tool. E.g., ngfx_environment should return {install_root: string, version: string, tool_paths: {[key]: string}, cache_dirs: {[key]: string}}. This enables LLMs to chain calls.
• Add parameter descriptions to all tools. For ngfx_deep_capture_capability_report, clarify: 'capture: path to .ngfx-capture or .ngfx-gfxcap file, or null to use default'; 'install_root: override NSIGHT_GRAPHICS_MCP_INSTALL_ROOT env var'; 'probe_cli_help: if true, invoke ngfx.exe --help to detect available CLIs'.
• Simplify tool names for clarity. Rename 'ngfx_deep_capture_capability_report' to 'ngfx_capture_capability_report' and 'ngfx_list_activities' to 'ngfx_list_ngfx_activities' to avoid confusion with generic 'activities'.
• Add error handling guidance. E.g., ngfx_environment description: 'If version is wrong, set NSIGHT_GRAPHICS_MCP_INSTALL_ROOT env var and call ngfx_environment(reload=true). If install not found, call ngfx_list_installs to see available paths.'
• Formalize parameter constraints. Use enums for probe_cli_help (true|false), add regex pattern for file paths (e.g., '.*\.(ngfx-capture|ngfx-gfxcap)$'), and document expected return codes for CLI tools.