Two tools with basic schemas but significant quality gaps. Tool names lack action verbs (git-changes-commit-message should be get_git_diff or extract_git_changes). Descriptions are present but generic, they don't explain WHEN to use each tool or dependencies between them. Parameter descriptions are minimal. No output schema documentation. Error handling returns raw error messages without recovery guidance. The push-changes tool is irreversible but lacks confirmation/dry-run pattern. No input validation or constraint documentation.

• Rename 'git-changes-commit-message' to 'get_git_diff' or 'extract_git_changes' to start with an action verb. Follow verb_noun convention.
• Document the output schema for get_git_diff: {modified: string[], added: string[], deleted: string[], details: {[filename]: string[]}}. Include field descriptions.
• Add a 'dry_run' boolean parameter to push-changes (default false). When true, return what would be committed without executing git push. Implements confirmation-request pattern.
• Enhance error messages with recovery guidance: 'Repository not found at /path/to/repo. Verify REPOSITORY_PATH env var or pass a valid git directory.' Include actionable next steps.
• Add constraints to 'message' parameter: min 10 chars, max 200 chars, no shell metacharacters. Document in description: 'Commit message (10-200 chars, alphanumeric + spaces/punctuation).' Validate server-side and return specific constraint violations.