The server exposes 39 tools across 10 modules with consistent naming conventions (verb-first: list_, create_, delete_, get_, start_, stop_, etc.) and basic parameter schemas. However, tool descriptions are extremely sparse (1-3 words), parameter descriptions are entirely absent, and output schemas are not documented. The codebase shows proper modular organization and type hints in Python, but the MCP tool definitions lack the detail required for LLMs to reason about tool selection, parameter values, or result handling. The server relies on user/agent knowledge of CML internals rather than self-documenting interfaces. Schema completeness varies: input parameters have types (string, number) but no descriptions or constraints (enums, ranges, formats). The pattern of missing parameter descriptions violates the critical check that 'every parameter needs a description explaining what it controls' and directly causes 100% parameter description failure across all 39 tools.

• Expand every tool description to 50-200 characters explaining: (1) what it does, (2) when to use it vs similar tools, (3) what it returns. Example for 'create_lab': 'Create a new lab (empty simulation environment) in CML. Use this to set up a new network topology project. Returns lab_id needed for subsequent node/link operations.'
• Add a description to every input parameter. Use the format: '<purpose>. <format/constraint>. <example if safe>.' Example for 'username' in create_user: 'Unique username for the new user. Must be 3-32 alphanumeric characters. Cannot contain spaces or special characters except underscore.'
• For parameters with enumerated values (annotation_type, resource_pool), declare the enum explicitly in the schema and document allowed values in the description. Example: 'annotation_type (enum: "text", "box", "rectangle", "freehand", "image"), the visual annotation style.'
• Document output schemas for all tools. Add a 'returns' section in each tool definition. Example for 'get_lab': 'Returns {lab_id: string, title: string, description: string, status: string ("stopped"|"running"|"staging"), created_at: ISO8601, node_count: integer}.'
• Add pagination parameters (limit, offset) to all list_* tools. Example: 'list_users(limit: 1-100 default 20, offset: 0 default 0) returns {users: [...], total_count: integer, has_more: boolean}.'
• Add range constraints to numeric parameters. Example for create_node: 'x (number, 0-10000): horizontal pixel coordinate. y (number, 0-10000): vertical pixel coordinate.'

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

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