Critical gaps across all 18 tools. No input schemas visible in provided source code, cannot verify parameter types, constraints, or descriptions. Tool descriptions are present but generic (10-50 chars), lacking WHEN/WHY context. No output schemas documented. No error handling guidance. Tools like 'github_auto_commit_and_pr' and 'github_full_merge_cycle' violate single-responsibility principle (combine multiple operations). Naming is verb-first (good), but descriptions do not explain dependencies, prerequisites, or recovery paths. No evidence of parameter validation, enum constraints, or field-level documentation.

• Add complete JSON Schema definitions for all 18 tools. Include type, description, enum constraints, and min/max for every parameter. Example: 'state' param for github_list_issues should be enum: ['open', 'closed', 'all'].
• Expand tool descriptions to 100-200 characters. Include WHEN to use (e.g., 'Use this to create a new issue when you have a title and optional body'), prerequisites (e.g., 'Requires repo_owner and repo_name'), and what it returns (e.g., 'Returns issue_id, url, and created_at').
• Document output schemas for all tools. Specify which fields are returned, their types, and which are safe to pass to downstream tools. Example: github_create_issue returns {issue_id: int, issue_url: string, created_at: ISO8601}.
• Split 'github_auto_commit_and_pr' into 'github_commit_changes' and 'github_create_pr' so agents can compose them independently. Similarly, split 'github_full_merge_cycle' into 'github_validate_pr_build', 'github_merge_pr', and 'github_delete_branch'.
• Add error handling guidance to descriptions. Example: 'If the issue is not found, returns 404 with available issue IDs. If you lack write permissions, returns 403, check repo access.' Include retryability hints for transient failures.