Hydra provides 5 tools with explicit schemas and descriptions, but quality is uneven. All tools have descriptions (10-100 chars) and input schemas with type definitions. However, descriptions are minimal (avg 65 chars vs baseline 194), lack context on WHEN to use tools, and omit recovery guidance. Parameters lack descriptions in 3/5 tools (hydra_status, hydra_metrics have empty properties). No output schemas documented. Error handling is absent, no guidance on retryability, user-fixable vs fatal errors, or recovery paths. Tool naming follows hydra_ convention but lacks verb clarity (hydra_restart vs restart_server). No tool annotations (readOnlyHint, destructiveHint) despite clear risk profiles. Composition is reasonable, each tool has one responsibility, but no chaining IDs documented.

• Document output schemas for all tools. E.g., hydra_status should return {state: string, pid: int, uptime_seconds: int, restarts_in_window: int, last_error: string, can_recover: bool}. hydra_logs should return {lines: string[], total_available: int}.
• Expand descriptions to 100-200 chars with WHEN-to-use context. E.g., 'Manually restart the supervised MCP server. Use when the server is unresponsive or after config changes. Blocks until restart completes (~5s). If restart fails, call hydra_status to check error state, then hydra_force_restart if needed.'
• Add descriptions to all parameters. E.g., hydra_restart.reason: 'Optional human-readable reason for restart (logged for audit). Max 256 chars.' hydra_logs.lines: 'Number of recent log lines to retrieve (1-500). Defaults to 50.'
• Add tool annotations via inputSchema or separate metadata. Mark hydra_restart and hydra_force_restart with destructiveHint=true. Mark hydra_status, hydra_logs, hydra_metrics with readOnlyHint=true. Mark hydra_restart with idempotentHint=true if safe to retry.
• Add error handling guidance in descriptions. E.g., 'If restart times out, the server may still be restarting, call hydra_status to verify. Retryable: yes. User-fixable: no, contact admin if persistent.'

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

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