Three tools with minimal documentation. All have descriptions (10-50 chars), but lack parameter descriptions and output schemas. Input schemas are present but sparse. No error handling guidance, no parameter constraints, no composition hints. Naming is acceptable (verb_noun pattern), but descriptions are too brief to guide LLM selection. No evidence of idempotency, pagination, or chaining support.

• Expand tool descriptions to 150-250 chars. Include: what the tool does, when to call it, what it returns, and any prerequisites. Example: 'List all active git worktrees across projects. Returns path, branch, and status for each. Call this first to discover available work contexts before querying specific worktrees.'
• Add parameter descriptions for all inputs. For 'change_id': 'Optional change ID (string, e.g. "I12345"). If omitted, returns all active loops. If provided, returns status for that specific loop only.' For 'worktree_path': 'Absolute or relative path to the worktree directory (e.g. "/home/user/projects/my-app"). Must be a valid git worktree.'
• Document output schemas for each tool. Example for list_worktrees: 'Returns array of {path: string, branch: string, status: string, last_commit: string}. Total count included for pagination planning.'
• Add error handling guidance. Example: 'If worktree_path does not exist, returns error with available paths. If Ralph loop not found, suggests similar change IDs. Errors are retryable unless marked fatal.'
• For list_worktrees, add pagination support: accept 'limit' (default 20, max 100) and 'offset' parameters. Return total_count so agents can iterate through large result sets without context explosion.