Server exposes 9 tools with basic descriptions and partial schemas. Most tools lack comprehensive parameter documentation and output schema definitions. Naming follows verb_noun convention (resolve, download, getConfig, updateConfig) but descriptions are generic and under-optimized for LLM selection. Parameter types are present but descriptions are sparse or missing. No error handling guidance, no output schemas documented, no tool annotations. This is a typical community server with significant gaps against production baselines.

• Document output schemas for all tools. E.g., resolve() should return {url: string, title: string, media: [{type: string, url: string}], ...}. Include field descriptions and types.
• Expand parameter descriptions with format, constraints, and examples. E.g., 'input: Share link from RedNote (xiaohongshu.com), Twitter (x.com), or Douyin (douyin.com). Accepts full URLs or shortened share links.'
• Move 'cookie' parameter to server-side configuration (updateConfig tool) or environment variable. Remove from resolve(), downloadDouyinViaExternalService(), batchResolve() signatures.
• Add error handling guidance to tool descriptions. E.g., 'If URL is invalid, returns error with suggestion to check link format. If media is unavailable, returns error with available alternatives.'
• Rename downloadDouyinViaExternalService to download_douyin_external or clarify in description when to use vs. download(). Add note: 'Use this only when external Douyin service is configured; otherwise use download().'
• Add tool annotations (readOnlyHint, destructiveHint) to distinguish safe tools (resolve, getConfig, getDiagnostics) from state-modifying ones (download, updateConfig, batchDownload).