Single tool with clear naming (repo_health_summary) and adequate description (97 chars). Input schema is present with proper type and description. However, output schema is completely undocumented, the tool returns JSON via text content with no declared structure, forcing LLMs to parse unstructured output. No error handling guidance, no parameter constraints beyond minLength=1, and no documentation of what fields the JSON response contains. Lacks idempotency hints and recovery guidance for common failure modes (missing git, invalid paths).

• Document the complete output schema in the tool description. Example: 'Returns {schemaVersion, checkoutPath, repositoryRoot, git: {isRepository, branch, head, dirty, staged, unstaged, untracked, conflicted}, project: {name, packageManager, scripts, expectedFiles}, health: {level, reasons}}'.
• Add error handling guidance: 'If checkoutPath does not exist, returns error with available parent directories. If git is not installed, isRepository will be false. If permission denied, returns error with required permissions.'
• Expand checkoutPath description: 'Absolute or relative path to a directory. Relative paths resolve from the server process working directory. Must be readable and a valid directory. Symlinks are resolved to their targets.'
• Clarify tool purpose in description: 'Analyzes a local repository checkout and returns health metrics including git status (branch, commits, conflicts), project metadata (name, package manager, scripts), and expected files (README, LICENSE, etc.). Use this to assess repository state before operations.'
• Add idempotency note: 'This tool is idempotent, repeated calls with the same checkoutPath return identical results (assuming filesystem state does not change between calls).'