Descriptions exist but are in Japanese and generic (e.g., 'テックブログを書く際に参考にすべきライティングスタイルです'). No parameter documentation, no output schema documentation, no error handling guidance. Tools are read-only style retrievers with no composition or chaining capability. Naming lacks action verbs (tech_blog_style, dazai_style, lp_style, off_topic_style are noun-based, not verb_noun). No pagination, no structured output definition, no recovery guidance.

• Rename tools to verb_noun pattern: get_tech_blog_style, get_dazai_style, get_lp_style, get_off_topic_style. This signals retrieval action to LLMs.
• Add English descriptions (50-150 chars each) following pattern: 'Retrieves [style name] writing guidelines. Use when user needs to write in [style]. Returns markdown with style rules, examples, and tone guidance.'
• Define output schema in tool registration: {type: 'object', properties: {text: {type: 'string', description: 'Full style guide markdown'}, style_name: {type: 'string'}, character_count: {type: 'integer'}}}.
• Add error handling that returns available styles on file-not-found: 'Style guide not found. Available: tech_blog_style, dazai_style, lp_style, off_topic_style. Try one of these.'
• Consider adding optional parameters (e.g., 'format': enum ['markdown', 'plaintext', 'json']) to increase tool flexibility and demonstrate schema usage to LLMs.