This server has 7 tools with basic naming (mostly get_/generate_ verbs) but significant quality gaps. Tool descriptions exist but are often generic (many under 100 chars) and lack context for LLM selection. Parameter descriptions are minimal or absent for critical parameters. Input schemas are present but lack proper validation constraints (no enums, no min/max bounds, no format specifications). Output schemas are completely undocumented, no tool specifies what fields its response contains. Error handling is absent from all tool definitions. Chinese language descriptions and parameter naming reduce LLM clarity. The server lacks tool annotations (readOnlyHint/destructiveHint) despite having both read and write operations. No pagination support visible despite tools that could return large results (get_chinese_herb_info, generate_herb_summary). Security concern: set_api_key exposes credentials as a tool parameter, violating secret-injection pattern.

• CRITICAL: Remove set_api_key as a tool. Use DOUBAO_API_KEY environment variable instead (already partially implemented in load_config()). Never expose secrets as parameters.
• Document output schema for every tool. Example: 'Returns {herb_name: string, properties: string[], effects: string[], safety_notes: string}'
• Convert free-form string parameters to enums where values are bounded: size → enum['512x512', '1024x1024', '2048x2048'], ratio → enum['9:16', '16:9', '1:1'], voice → enum of actual supported voices
• Add explicit numeric constraints in schemas: duration as integer with minimum 1, maximum 60; speed as number with minimum 0.5, maximum 2.0
• Add tool annotations to all tools: readOnlyHint=true for get_*, generate_audio_from_text; destructiveHint=true for set_api_key (or remove it), combine_herb_video
• For each tool, add error handling block in description: 'Returns error if [condition], user should [action]'. Example: 'If herb not found, returns error with available herb names for correction.'
• Translate parameter descriptions to English for MCP protocol clarity, while keeping tool descriptions contextually appropriate
• Add pagination support if tools can return large lists. E.g., get_chinese_herb_info could return paginated properties/effects.
• Convert herb_info parameter in generate_herb_summary from JSON string to structured object with documented fields (name, properties, effects, etc.)
• Document expected URL format for video_url and audio_url parameters in combine_herb_video; add URL validation error guidance