Two tools with basic schemas and Chinese descriptions. parse_douyin has a clear single parameter (share_url) with type and description; get_tiktok_trending has limit with type, default, and description. However, both descriptions lack English translations and are moderately detailed (100-150 chars). Output schemas are NOT documented, the code shows format_video_info() returns formatted text, but no structured schema is declared. No error handling guidance in descriptions. No parameter validation constraints (e.g., limit bounds for get_tiktok_trending). Tool names follow verb_noun pattern (parse_*, get_*), which is good. Risk annotations (READ_ONLY) are present but not exposed as toolAnnotations in the MCP schema.

• Add structured output schema to both tools. E.g., parse_douyin should return {title: string, author: string, duration_sec: number, cover_url: string, play_url: string, music_url: string} instead of formatted text.
• Provide English descriptions (50-200 chars) alongside or instead of Chinese. E.g., 'Parse Douyin share links (v.douyin.com or iesdouyin.com) to extract video metadata: title, author, duration, cover, watermark-free video URL, and music URL.'
• Add parameter constraints: get_tiktok_trending limit should be 1 - 100 (default 15). Document in description: 'Number of trending videos to return (1 - 100, default 15).'
• Document error handling in descriptions. E.g., 'Returns error if URL is invalid or API structure changes. Retry with a different link or check if Douyin has updated its page structure.'
• Register toolAnnotations in MCP schema. Both tools are read-only and idempotent, expose readOnlyHint: true and idempotentHint: true in tool definitions.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry