Facebook MCP server has clear tool naming (verb_noun pattern) and complete input schemas with Zod validation. All 7 tools have descriptions and typed parameters with enums where appropriate. However, descriptions are terse (avg ~60 chars, below the 194-char baseline), lack WHEN/WHY context, and omit dependency hints. Output schemas are undocumented, LLMs cannot predict response structure. Error handling returns raw API errors without recovery guidance. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Missing idempotency guidance for write operations.

• Expand tool descriptions to 100 - 200 chars. Include WHEN to use (e.g., 'Use schedule_post to publish at a specific future time; use post_to_page for immediate publication'). Add dependency hints: 'Call get_recent_posts first to retrieve post IDs for deletion.'
• Document output schemas explicitly. E.g., get_recent_posts returns [{id, message, created, likes, comments, shares}]. Specify field types and whether lists are paginated.
• Add tool annotations: mark post_to_page, schedule_post, post_photo with destructiveHint=false (writes but not destructive); mark delete_post with destructiveHint=true; mark all read tools with readOnlyHint=true.
• Enhance error handling: categorize errors (e.g., 'Invalid post_id format (retryable: false). Expected format: pageId_postId. Example: 123456_789012.') and suggest recovery actions.
• Add a confirm_delete_post tool or dry-run parameter to delete_post. Return a confirmation token that must be passed to execute the deletion, preventing accidental data loss.