Critical gaps across all dimensions. Tool definitions lack visible input schemas in source code, cannot verify parameter types, descriptions, or constraints. Module-level descriptions are generic ('Tool module for...') rather than LLM-optimized action descriptions. No evidence of enum constraints, format specifications, or error recovery guidance. 15 tools with minimal introspection available. Naming follows verb_noun pattern (discovery, messages, channels) but descriptions do not explain WHEN to use each tool or what distinguishes overlapping tools (e.g., discovery vs stats vs analytics). No pagination, output schema documentation, or chaining-ID patterns visible. Security-sensitive tools (moderation, permissions, members) lack permission-gate or audit-trail documentation.

• Extract and document input schemas for all 15 tools. Each parameter must have: name, type (string|number|boolean|array|object), description (50-150 chars), and constraints (enum, min/max, pattern, required). Use JSON Schema format in tool registration.
• Rewrite tool descriptions as action-oriented prompts (50-200 chars). Example: 'List all Discord guilds the bot has access to. Use this first to discover available servers before querying channels or members.' Include WHEN to use and what distinguishes from similar tools.
• Add parameter descriptions to all tools. For each parameter, explain: what it controls, valid values/ranges, format (e.g., 'ISO 8601 date'), and whether it's required. Example: 'guild_id (required, string): The Discord server ID. Get from discovery tool.'
• Implement pagination for list-returning tools (discovery, messages, members, stats, analytics). Add limit (default 20, max 100) and cursor/offset parameters. Document result count and next_cursor in output schema.
• Add confirmation/dry-run patterns to destructive tools (moderation, delete_channel, remove_member, delete_role). Example: 'dry_run (boolean, default true): If true, show what would be deleted without executing. Set to false to confirm deletion.' Document permission requirements and audit logging.