24 tools with significant quality gaps. Tool names follow verb_noun convention (get_config, set_prefs, config_perm_add) but descriptions are inconsistent: many are terse Korean-language strings (e.g., 'Claude 설정 introspection') that lack English clarity and actionable context. Input schemas are present but sparse, most parameters lack type constraints (enums, ranges, patterns). Output schemas are undocumented. Error handling is minimal; tools shell out to Python scripts but responses are JSON-wrapped without recovery guidance. No pagination support despite tools returning lists (get_tracked, get_file_history). Parameter descriptions are often single-phrase Korean text without format/constraint details. Tool composition is reasonable (separate read/write tools) but parameter naming inconsistencies (e.g., 'project' parameter is overloaded, accepts folder name OR path, documented only in description, not as separate params). Security: no visible input validation, secrets not explicitly injected, no audit logging in tool definitions.

• Translate all tool descriptions to English and expand to 50 - 200 characters. Include WHAT the tool does, WHEN to use it, and WHAT it returns. E.g., 'get_config: Retrieve Claude configuration for tracked projects. Returns normalized sections (permissions, hooks, plugins, agents, skills). Call this first to inspect current settings before making changes.'
• Split overloaded 'project' parameter into separate 'project_name' and 'project_path' parameters, or add an enum constraint listing valid project names. Document which parameter takes precedence if both are provided.
• Document output schemas for all tools. For get_config, specify: {sections: {permissions: [...], hooks: [...], plugins: [...], agents: [...], skills: [...]}, timestamp: ISO8601}. For list tools, include total_count and next_cursor for pagination.
• Add error recovery guidance to tool descriptions. E.g., 'If the Python script times out (>60s), retry with a smaller project set. If JSON parsing fails, check that .claude directories are readable.'
• Add input validation hints to parameter descriptions. E.g., 'kind must be one of: allow, deny, ask' (use enum in schema). 'rule: permission rule pattern (e.g., path/to/file.json)'. 'matcher: optional glob pattern (e.g., *.json)'.