Strong schema definitions with Zod validation, clear tool naming (verb_noun pattern), and comprehensive parameter constraints. All 8 tools have descriptions and input schemas. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present and correct. However, descriptions are brief (avg ~60 chars, below the 194-char baseline), lack dependency hints, and some parameter descriptions are minimal. Error handling redacts secrets but lacks recovery guidance. Output schema is not documented.

• Expand tool descriptions to 100 - 200 chars. Add WHEN to use (e.g., 'Use feishu_search to find content by keyword; use feishu_list_wiki to browse a folder hierarchy'). Include prerequisites (e.g., 'Requires prior Feishu authorization').
• Document output schemas in tool descriptions or a separate schema reference. E.g., 'Returns {items: Array<{id, title, type, url}>, cursor?: string, total?: number}' for list tools.
• Enhance error messages with recovery guidance. Instead of 'Invalid revision_id', return 'Invalid revision_id. Call feishu_read(target) to fetch the current revision_id, then retry feishu_edit().'
• Clarify parameter formats in descriptions. For 'parent' and 'target', specify: 'A Feishu URL (e.g., https://feishu.cn/wiki/...) or a document token (alphanumeric string).'
• Add a 'dry_run' boolean parameter to feishu_edit and feishu_create to allow agents to preview changes before committing. Return the proposed changes without persisting them.