Discord MCP server has 8 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-50 chars, mostly short), and input schemas are present with parameter types. However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool or what happens next. Parameter descriptions are minimal (e.g., 'The ID of the Discord channel' repeated 5 times). No output schemas documented. Error handling returns formatted strings but lacks recovery guidance or error classification. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Missing idempotency guidance for write operations. Naming is verb-first and clear (send_message, get_channel, delete_message), which is good. However, parameter naming inconsistencies: 'limit' is a string type (should be integer), and 'channelId' vs 'guildId' use camelCase inconsistently with Discord API conventions.

• Expand tool descriptions to 50-200 chars. Include WHEN to use (e.g., 'Call this to retrieve recent messages before responding to a user'), prerequisites (e.g., 'Requires bot to have read permissions'), and what the response contains (e.g., 'Returns message IDs, authors, timestamps, and content').
• Define output schemas for all tools. Return structured JSON with typed fields (e.g., {messages: [{id: string, author: string, content: string, timestamp: string}], total: number}) instead of formatted strings.
• Fix parameter type for 'limit' in get_messages: change from string to integer with minimum 1, maximum 100.
• Add tool annotations: mark delete_message and edit_message with destructiveHint=true; mark get_* tools with readOnlyHint=true; mark send_message and create_channel with idempotentHint=false (not idempotent).
• Enhance error messages with recovery guidance. E.g., 'Channel not found (ID: xyz). Try list_channels(guildId) to find valid channels.' Classify errors: retryable (network timeout), user-fixable (invalid channel ID), fatal (permission denied).

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

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