Single tool with clear naming (search_icons) and reasonable description (127 chars, within 10-1024 range). Input schema present with proper types and descriptions for both parameters. However, output schema is NOT documented, the tool returns structured data (page, pageSize, total, totalPages, count, icons array with id/name/svg fields) but this is only visible in implementation code, not in the tool definition. No error handling guidance for LLMs (e.g., what to do if keyword is empty or API fails). Missing output schema documentation is a critical gap per pattern:tool and pattern:response-shaper.

• Add explicit output schema to tool definition: {type: 'object', properties: {page: {type: 'number'}, pageSize: {type: 'number'}, total: {type: 'number'}, totalPages: {type: 'number'}, count: {type: 'number'}, icons: {type: 'array', items: {type: 'object', properties: {id: {type: 'string'}, name: {type: 'string'}, svg: {type: 'string'}}}}}}
• Enhance error messages with recovery guidance: 'keyword is required and must be non-empty' instead of generic 'keyword is required'; 'API returned error: {message}. Try a simpler keyword or check iconfont.cn status' for API failures.
• Add page parameter constraints to schema: {type: 'number', minimum: 1, maximum: 1000, description: 'Page number (1-1000), 10 icons per page. Start with page 1.'}
• Document result limits in description: 'Returns up to 10 icons per page. Use page parameter to fetch additional results. Recommend stopping after 5-10 pages (50-100 icons) to avoid excessive API load.'
• Update protocolVersion to '2026-07-28' and adopt stateless request handling with per-request _meta logLevel support.