37 tools with consistent verb-noun naming (list_, get_, publish_, delete_, etc.). All tools have descriptions (10-150 chars, mostly adequate). Input schemas present for all tools with typed parameters. However, descriptions are often terse (e.g., 'List posts from a Facebook Page' lacks context on when to use vs. list_reels). Parameter descriptions are minimal, most are 1-2 phrases without format/constraint guidance. Output schemas are not documented in the source. Error handling and recovery guidance are absent. No confirmation pattern for destructive operations (delete_post, delete_comment). Risk annotations present (READ_ONLY, WRITE, DESTRUCTIVE) but not integrated into descriptions. Pagination parameters (limit) present but no documentation of defaults, max values, or cursor/offset behavior.

• Document output schemas for all tools. For list_posts, specify: {posts: [{id, message, created_time, likes_count}], total_count, next_cursor}. For get_page, specify all returned fields.
• Add confirmation/dry-run pattern to delete_post and delete_comment. E.g., add a 'confirm' boolean param or a separate 'preview_delete_post' tool that shows what would be deleted.
• Expand parameter descriptions with format/constraint guidance. E.g., 'metric' in page_insights should list valid values (page_views, page_fans, page_engaged_users, etc.). 'limit' should specify range (1-100, default 20).
• Add error recovery hints to tool descriptions. E.g., publish_post: 'If page not found, call list_pages() to verify access. If rate-limited, wait 60 seconds before retrying.'
• Document pagination behavior in list_* tools. Specify: default limit, max limit, whether cursor or offset is used, and how to detect end of results.

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

• Relies on Sampling (deprecated) - integrate directly with the LLM provider API