Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. execute-lean and execute-lean-persistent have minimal descriptions (under 50 chars). Parameter descriptions are present but generic. No output schemas documented. No error recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Missing idempotency guidance for persistent sessions. Naming is clear (verb_noun pattern), but composition could be improved, execute-lean-persistent requires manual session_id management, forcing agents to track state.

• Expand tool descriptions to 100-200 chars. For execute-lean: 'Execute Lean4 code in a transient Docker container. Each call creates a fresh container, discarding state. Use for isolated code snippets. Returns stdout, stderr, and exit code. Fails if Lean syntax is invalid or Docker is unavailable.'
• Document output schemas explicitly. Define: { stdout: string, stderr: string, exit_code: int, execution_time_ms: int, container_id: string }. Include in tool description or as a separate schema field.
• Add tool annotations: execute-lean and execute-lean-persistent with destructiveHint=true (they spawn containers and consume resources). cleanup-session with destructiveHint=true (irreversible deletion).
• Add error recovery guidance to descriptions. E.g., 'If compilation fails, check syntax with lean --check. If Docker is unavailable, verify Docker daemon is running. Retryable errors: timeout, resource exhaustion. Non-retryable: syntax errors, missing imports.'
• For execute-lean-persistent, document session lifecycle: 'Sessions persist until cleanup-session is called or max_age is exceeded. Idempotent: calling with the same code twice produces the same result. Always call cleanup-session when done to free resources.'

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

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