Worktree Manager MCP has 13 tools with basic naming and schema structure, but significant gaps in descriptions and parameter documentation. All tools have names starting with action verbs (list_, create_, delete_, etc.), which is good. However, most tool descriptions are extremely brief (10-30 chars), falling well below the 50-200 char baseline for LLM-optimized descriptions. Parameter descriptions exist but are minimal ('Name of the worktree'). Input schemas are present with type definitions, but lack constraints (enums, ranges, patterns). No output schemas are documented. Error handling is absent, no recovery guidance, no categorization of error types. The tool set is well-composed (single responsibility per tool, good naming distinctions), but the descriptions are too terse to guide LLM selection effectively.

• Expand tool descriptions to 80-150 chars. Example: 'create_worktree' → 'Create a new git worktree from a base branch. Worktree names must be unique and alphanumeric. Returns the new worktree path and status.'
• Document output schemas for all tools. Example: list_worktrees should return {worktrees: [{name, path, branch, is_archived, is_locked}], total_count}.
• Add parameter constraints in descriptions. Example: 'name (string, 1-50 alphanumeric chars, no spaces)' instead of just 'Name of the worktree'.
• Implement error recovery guidance. Example: 'Worktree not found. Call list_worktrees() to see available worktrees.' for 404 errors.
• Add confirmation step for destructive operations. Example: delete_worktree should support a 'confirm=true' parameter or return a confirmation token requiring a second call.