14 tools with consistent naming (verb_noun pattern) and descriptions present. All tools have input schemas with typed parameters and descriptions. However, output schemas are not documented in the source code, parameter descriptions lack detail on constraints/formats, and error handling guidance is minimal. Tool names are clear and action-oriented (list_, get_, post_, delete_, save_), but descriptions are brief (avg ~60 chars) and lack context on when to use each tool or what to expect in responses. No enum constraints visible for privacy_level or other constrained inputs. Confirmation parameters (confirm: boolean) are present on destructive operations, which is good practice.

• Document output schemas for all tools. Specify field names, types, and what each field represents. E.g., get_videos should document: returns array of {video_id, title, view_count, like_count, publish_date, ...}.
• Add enum constraints to privacy_level parameter. In post_video and post_photos descriptions, state: 'privacy_level must be one of the values returned by get_creator_info for this account'.
• Expand parameter descriptions with format/constraint details. E.g., 'limit: Maximum number of videos to return (1-100, default 20)' instead of just 'Maximum number of videos to return'.
• Enhance tool descriptions with dependency hints and use-case guidance. E.g., 'Call get_creator_info first to retrieve valid privacy_level values for this account before calling post_video.'
• Add error recovery guidance to destructive operations. E.g., post_video: 'If moderation fails, check get_post_status(publish_id) to see the rejection reason. Revise and retry with a new post_video call.'