bb-mcp defines 20 tools with basic schemas and descriptions in Korean. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are minimal (10-50 chars), lack actionable context for LLM selection, and omit prerequisites or recovery guidance. No output schemas are documented. Tool names use inconsistent prefixes (bb_pr_*, bb_file_*, bb_allowlist_*) but lack verb-noun clarity, 'bb_pr_inbox' is ambiguous (list? fetch?). Parameters lack enums for constrained values (e.g., 'state' in bb_pr_inbox accepts 'OPEN, MERGED, DECLINED, SUPERSEDED' but is a free-form string). Error handling is absent from tool definitions. Security-critical tools (bb_pr_merge, bb_pr_decline) lack confirmation patterns or dry-run support.

• Expand all descriptions to 50-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. E.g., 'List all pull requests in allowed repos, filtered by state (OPEN/MERGED/DECLINED/SUPERSEDED). Returns PR ID, title, author, state. Use this to discover PRs before calling bb_pr_summary for details.'
• Document output schemas for all tools. Specify returned fields, types, and whether results are paginated. E.g., bb_pr_inbox returns {prs: [{id, title, state, author, created_at}], total_count, next_cursor}.
• Convert constrained parameters to enums. Change bb_pr_inbox.state from string to enum: ['OPEN', 'MERGED', 'DECLINED', 'SUPERSEDED']. Change bb_pr_merge.merge_strategy to enum: ['merge_commit', 'squash', 'fast_forward'].
• Add confirmation pattern for irreversible tools. bb_pr_merge and bb_pr_decline should support a 'dry_run' parameter or return a confirmation token requiring a second call with 'confirm=true'.
• Rename tools for clarity: bb_pr_inbox → list_prs, bb_doctor → check_credentials, bb_pr_summary → get_pr_summary, bb_file → get_file_content. Use consistent verb_noun pattern across all 20 tools.