This server has clear tool definitions with explicit schemas and descriptions visible in app/mcp/server.py. All 10 tools are registered with names following verb_noun patterns (docker_health, list_containers, get_container, start_container, stop_container, restart_container, list_images, get_container_logs, get_container_stats, docker_version). Descriptions are present and actionable (average ~80-120 chars, within baseline range). However, several critical gaps prevent a higher score: (1) Most parameters lack explicit type constraints and validation guidance in descriptions; (2) No output schemas are documented, LLMs cannot see what fields they receive; (3) Error handling is completely absent, no guidance on what to do if a container is not found, or if Docker daemon is unreachable; (4) No parameter descriptions for many fields (e.g., 'timeout' in restart_container says 'Timeout in seconds before killing the container (default: 10)' but lacks guidance on valid range or what happens if exceeded); (5) No idempotency hints for reversible operations (start/stop/restart can be safely retried, but this is not declared); (6) Schemas are minimal, many lack descriptions for required parameters (e.g., 'container_id' in get_container has description, but response structure is never defined). Tools operate on Docker resources (containers, images, stats) which are well-defined, but the interface obscures this. Average description length is good (~100 chars), but parameter annotations are sparse or missing entirely.

• Document output schemas for all tools. For example, docker_health should declare it returns {status: string, container_count: number, memory_usage: {total: number, available: number}, cpu_count: number}. Use JSON Schema format or TypeScript interfaces visible in the code.
• Add error handling to tool descriptions. E.g., get_container: 'Returns container details or error if not found. If container_id is invalid, error will suggest available containers via list_containers().'
• Declare idempotency and destructiveness hints. Add toolAnnotations support: start_container, stop_container, restart_container should use destructiveHint=true or idempotentHint=true to signal to LLMs that retry is safe.
• Specify valid ranges and formats for numeric parameters. For 'tail': 'Number of lines to return from the end (1-10000, default: 100)'. For 'timeout': 'Timeout in seconds before force-killing (1-3600, default: 10)'.
• Clarify container_id parameter format. Add: 'Accepts full container ID (12+ hex chars), short ID (first 3+ chars), or container name. Example: abc123def456 or my-app or abc.'
• Add parameter constraints to schema. Use 'minimum' and 'maximum' properties in JSON Schema: {"type": "integer", "minimum": 1, "maximum": 10000, "default": 100} for tail parameter.
• Document list behavior and pagination. list_containers and list_images should declare result limits (e.g., 'Returns up to 100 containers; for more, use Docker API directly') and whether results are paginated.
• Add status/state field descriptions. For list_containers and get_container, document what status values mean (created, restarting, running, removing, paused, exited, dead) and when each appears.

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

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