Server has 12 tools with explicit Zod schemas and descriptions. Naming follows verb_noun pattern (discord_*). However, descriptions are inconsistent in depth, some are 50-80 chars (good), others are 150+ chars (verbose). Parameter descriptions are present but often generic ('Discord channel ID' repeated 20+ times). Admin tools expose a generic 'data' parameter accepting free-form JSON, which invites hallucination and bypasses schema validation. No output schema documentation. Error handling is minimal, most tools return raw Discord API responses without recovery guidance. Security: credentials are server-side injected (good), but admin tools lack permission checks or audit logging hints.

• Replace generic 'data' parameter in admin tools with explicit, typed fields. E.g., discord_admin_server update should accept {name, description, icon_url, ...} instead of free-form JSON. This enables schema validation and LLM reasoning.
• Document output schemas for all tools. Include field names, types, and descriptions. For list tools, add pagination (limit, offset, total_count) and cap results at 50 items. Example: discord_list_channels returns [{id, name, type, topic, created_at}, ...] with total_count.
• Add permission checks and audit logging to admin tools. Verify caller has 'admin' or 'moderator' role before executing destructive ops. Log caller_id, operation, parameters, timestamp, and result to stderr or a structured log.
• Enhance parameter descriptions with format, constraints, and selection guidance. E.g., 'channelId (Discord snowflake, 18-20 digits), use discord_list_channels to discover available channels.' Add examples of valid values for enums.
• Wrap Discord API errors with recovery guidance. E.g., if send_message fails with 'Missing Permissions', return 'Bot lacks Send Messages permission in this channel. Ask a server admin to grant it.' If channel not found, return 'Channel not found. Available channels: [list]'.