This server exposes 3 tools via a YAML configuration file (stack.yaml), not through explicit code registration. Tool definitions are inferred from the YAML allow-list, not directly visible in source code. No input schemas, parameter descriptions, or output schemas are documented anywhere in the provided code. Descriptions are minimal (10-30 chars) and lack context for LLM selection. No error handling, validation, or recovery guidance is present. The tools appear to be thin wrappers around a Containerlab API server, but the actual tool implementation is not shown, only the gateway configuration.

• Create explicit tool registration with full JSON Schema input definitions. For each tool, document required/optional parameters, types (string, number, boolean, enum), and constraints (min/max, regex patterns, allowed values).
• Expand descriptions to 50-200 characters. Example: 'authenticate' → 'Authenticate with the Containerlab API server using provided credentials. Returns an auth token required for subsequent API calls. Call this first before inspectLab or listLabs.'
• Document output schemas for each tool. Specify what fields are returned (e.g., authenticate returns {token, expires_at}, listLabs returns {labs: [{name, status, nodes}], total_count}).
• Add parameter descriptions. For authenticate: explain what credentials are needed (username, password, or token). For inspectLab: document what topology_id or node_filter parameters do.
• Implement error handling with recovery guidance. E.g., 'Authentication failed: invalid credentials. Verify API_USERNAME and API_PASSWORD environment variables are set correctly.'