18 tools with mixed quality. Naming is generally verb-first and clear (roll, query_rules, sync_byod, etc.), following pattern:tool conventions. However, descriptions are inconsistent: some are adequate (roll, query_rules), others are vague or missing context (discord_post vs discord_webhook are near-duplicates; session action parameter lacks clarity on what 'create' vs 'load' vs 'save' actually do). Input schemas are present but sparse, most parameters lack detailed constraints, ranges, or enum values. No output schemas documented anywhere. Error handling is absent from descriptions. Several tools expose implementation details (webhook_url as a parameter) rather than abstracting credentials. Composition issues: discord_post and discord_webhook do nearly identical things; session management tools lack clear state model documentation.

• Consolidate discord_post and discord_webhook into a single send_discord_message tool with optional payload parameter. Remove webhook_url from parameters; inject it server-side via environment variable keyed by a channel/target name.
• Document output schemas for all tools. For query_rules, return {results: [{name, description, system, type}], total_count}. For list_byod_files, return {files: [{id, name, size, chunks}]}. Include these in tool descriptions or a separate schema reference.
• Expand session tool description: 'Manage game session state. Actions: create (new session, returns session_id), load (restore from disk, requires session_id), save (persist current state, requires session_id), list (enumerate all sessions, returns [{session_id, created_at, last_modified}]).'
• Add error handling guidance to destructive/write tools. E.g., clear_byod: 'Permanently deletes all BYOD data. Returns {deleted_count, freed_bytes}. On failure, returns {error, reason, recovery_hint}. This operation is irreversible.'
• Add enum constraints to parameters. query_rules 'system' param should declare enum: ['ogl', 'dw', 'brp', '5ecompatible', 'orcus', 'osr']. roll_table 'roll' param should specify range (e.g., 1 - 20 for d20). Enums prevent hallucinated values.