Server has 2 tools with reasonable naming and basic descriptions, but significant gaps in parameter descriptions, schema documentation, and error handling guidance. Both tools are write operations but lack confirmation/dry-run patterns. Output schemas are not documented. Parameter descriptions exist but are minimal (10-30 chars). Tool names start with action verbs (discord-send-*) which is good, but descriptions lack context about when to use each tool and what they return. Error handling returns structured responses but lacks recovery guidance. No tool annotations (destructiveHint critical for write operations). This is a functional but below-average MCP server that would benefit from richer parameter docs and output schema documentation.

• Add explicit output schema documentation to both tools: 'Returns {content: [{type: string, text: string}], isError: boolean}' in tool description or separate schema field.
• Add destructiveHint annotations to both tools: mark them as destructive operations so agents know these calls have irreversible side effects.
• Expand parameter descriptions: 'webhookUrl' should include 'Discord webhook URL (must start with https://discordapp.com/api/webhooks/ or https://discord.com/api/webhooks/)'.
• Document embeds parameter format: 'Array of Discord embed objects, each with title, description, color (decimal), fields array, footer. Max 10 embeds per message. Field limits: title max 256 chars, description max 2048 chars, field value max 1024 chars.'
• Add recovery guidance to error responses: instead of just 'Error: Discord API Error...', return 'Invalid webhook URL or insufficient permissions. Verify the webhook URL and that the bot has message send permissions.'
• Document autoFormat dependency: add to discord-send-embed description: 'If autoFormat=true, requires OPENAI_API_KEY environment variable and calls GPT-4 to format content. Incurs API costs.'
• Add content length constraints: describe maximum message length and embed limits (Discord has 2000 char limit for content, 4096 for embed descriptions).
• Consider adding a dry-run mode or validate-webhook tool to let agents test connectivity before sending production messages.
• Clarify when to use each tool: discord-send-message for simple text, discord-send-embed for rich formatting with embeds. Current descriptions don't guide this choice.