The server defines 17 tools with mixed quality. The primary `consensus` tool has a well-structured JSON schema with 11 optional parameters, clear descriptions, and proper type constraints (e.g., maxRounds 1-10, participantTemperature 0-2). However, 16 preset-specific tools (consensus_code_review, consensus_architecture_debate, etc.) lack visible input schemas in the source code, only tool names and brief descriptions are shown. Descriptions are present but generic (e.g., 'Expert-panel preset tool for code review consensus'). The consensus tool description is strong (~180 chars), but preset tools average ~80 chars and lack actionable guidance on when to use each. No parameter descriptions visible for preset tools. Error handling and output schemas are not documented in the provided code.

• Provide explicit input schemas for all 16 preset tools in the tool registration. Each should document the 'prompt' parameter (required, string, min 1 char) and any preset-specific overrides (e.g., consensus_security_redteam might expose a 'threat_model' param). Reference: pattern:tool.
• Expand preset tool descriptions to 100-150 chars. Include: (1) what domain/use case it targets, (2) which expert panel it applies, (3) when to use this vs the generic consensus tool. Example: 'Run consensus with a security red-team panel. Use this for threat modeling, vulnerability assessment, and attack-surface analysis. Applies security_redteam preset with tuned defaults.'
• Document output schema for the consensus tool and all presets. Specify: consensus_score (number 0-100), rounds_completed (int), participant_responses (array of {participant_id, position, confidence}), judge_synthesis (string if judge=true), convergence_status (string: 'converged'|'max_rounds'|'error'). Reference: pattern:tool.
• Add parameter descriptions for memory-dependent tools. E.g., consensus_recall: 'prompt (required, string): Query to search past decisions. Returns matching decisions from project memory if enabled, else error with guidance to enable memory in config.' Reference: pattern:tool-description.
• Implement error handling with recovery guidance. E.g., if a participant is unavailable, return: 'Participant X unavailable. Retry with participantIds excluding X, or check participant config.' If memory is not enabled, return: 'Memory not enabled. Enable in consensus.config.json and restart server.' Reference: pattern:recovery-guide.