Tierward exposes 10 tools (5 primary + 5 deprecated aliases) with minimal parameter complexity but significant documentation gaps. All tools are read-only and stateless, which is positive. However, descriptions lack LLM-optimized guidance on WHEN to use each tool vs. alternatives, parameter descriptions are sparse or missing, and output schemas are not formally documented. Tool names follow verb_noun convention (tierward_doctor_report, tierward_team_settings) but descriptions are terse (avg ~100 chars, below the 194-char baseline for A+ tools). No error handling guidance, no recovery paths, and deprecated aliases dilute the interface without clear migration messaging.

• Document output schemas for all tools. For tierward_doctor_report, specify: { checks: Array<{ name: string, status: 'pass'|'fail', details?: string }>, summary: { passed: number, failed: number } }. This enables LLMs to extract and reason about results.
• Remove or clearly deprecate cdk_* aliases. If migration is needed, add a deprecation notice in each alias description: 'DEPRECATED: Use tierward_* instead. This alias will be removed in v3.0.0.' Provide a single canonical tool per function.
• Expand descriptions to 150 - 250 characters with explicit WHEN-to-use guidance. Example: 'tierward_team_settings: Returns governance rules from .claude/team-settings.json. Call this FIRST to check if the project is governed; if absent, the project is unrestricted. Use before tierward_doctor_report to understand context.'
• Add error handling guidance to tierward_pr_review: 'Requires gh CLI authenticated. If gh is not installed, returns error with install instructions. If user is not authenticated, returns error with 'gh auth login' command.'
• Document prNumber parameter format: 'GitHub PR number (positive integer, e.g. 42). Must be a PR in the current repository. Returns error if PR does not exist.'