Server defines 6 tools with basic schemas and descriptions in Chinese. All tools have input schemas with type definitions and parameter descriptions, meeting minimum requirements. However, descriptions are terse (avg ~80 chars, below 194-char baseline), lack WHEN-to-use guidance, and omit output schema documentation. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Parameter descriptions are minimal. Error handling and recovery guidance absent. Tool names follow verb_noun pattern (list_, search_, analyze_, summarize_, generate_) but lack English descriptions for non-Chinese-speaking agents. No pagination support documented for list_knowledge_bases despite potentially large result sets.

• Add output schema documentation for all tools. Define return type (object/array), field names, types, and descriptions. E.g., search_knowledge should document: {results: [{id, title, content, score}], total_count, next_cursor}.
• Expand descriptions to 100-200 chars and include WHEN-to-use guidance. E.g., 'analyze_log: Parses application/ops logs to identify error patterns, exception types, and severity distribution. Use when debugging failures or analyzing crash dumps.'
• Add English translations of all descriptions. Provide both Chinese and English so multilingual agents can understand tool purpose.
• Declare tool annotations in schema: add 'readOnlyHint: true' to all tools to signal they are safe to retry and have no side effects.
• Document error cases and recovery paths. E.g., 'search_knowledge: Returns empty results if knowledge base not found. Call list_knowledge_bases() first to verify the knowledge base name.'