Server has 6 tools with basic schemas and Japanese descriptions. Critical issues: (1) All descriptions are in Japanese, limiting LLM comprehension in English-first environments. (2) Descriptions are extremely short (10-20 chars), below the 34-char p10 baseline. (3) Only one component ('Button') is supported despite enum comments suggesting future expansion, schema is artificially constrained. (4) Parameter descriptions exist but are minimal ('コンポーネント名'). (5) No output schema documentation. (6) get-component-example tool returns props instead of examples (logic error). (7) No error handling or recovery guidance. (8) Tool names are clear (verb_noun pattern) but descriptions fail to explain WHEN to use each tool or distinguish overlapping functionality (e.g., get-component vs get-component-props vs get-component-example).

• Translate all tool descriptions to English and expand to 50-150 chars. Example: 'get-component' → 'Retrieve complete component documentation including props, examples, and usage guidelines for a specified component.'
• Document output schemas explicitly. Define the structure of PROPS and EXAMPLES objects so LLMs know what fields to expect (e.g., 'Returns {props: {name: string, type: string, required: boolean}[], examples: {code: string, description: string}[]}')
• Fix get-component-example: change 'const props = PROPS[componentName]' to 'const example = EXAMPLES[componentName]' to return actual examples, not props.
• Expand componentNameSchema from single 'Button' literal to union of all available components. Uncomment and populate the union based on Object.keys(EXAMPLES) and Object.keys(PROPS).
• Add error handling: validate componentName exists in PROPS/EXAMPLES before accessing; return structured error with available component list if not found (pattern: recovery-guide).