Server has 10 tools with clear verb-noun naming (list_*, set_*, pin_*, find_*, wan_*, rename_*, remove_*, reboot). Descriptions are present and moderately detailed (50-200 chars typical), explaining WHAT each tool does and key parameters. Input schemas are visible with type declarations and parameter descriptions. However, output schemas are NOT documented, LLMs cannot predict return structure. Error handling is minimal; no recovery guidance or actionable error messages. Write tools lack confirmation/dry-run patterns despite destructive risk (reboot, remove_static_lease). Parameter descriptions could be more precise on constraints (e.g., MAC format, IP range validation). No tool annotations (readOnlyHint/destructiveHint) despite clear risk stratification in the code.

• Document output schemas for all tools. E.g., list_devices returns [{ip: string, mac: string, name: string, lease_remaining_seconds: number}, ...]. Include pagination (total_count, next_cursor) for list tools.
• Add tool annotations to schema: readOnlyHint=true for list_* and find_free_ip; destructiveHint=true for reboot; idempotentHint=true for set_static_lease (if idempotent). Expose via FastMCP tool registration.
• Implement confirmation pattern for reboot and remove_static_lease. Return {status: 'confirmation_required', message: 'Reboot will disconnect all devices. Confirm?'} and require a confirm_reboot(confirmed=true) follow-up call.
• Add formal parameter constraints: MAC address regex pattern (aa:bb:cc:dd:ee:ff), IP address format, identifier matching rules. Use JSON Schema pattern/enum fields, not just prose descriptions.
• Enhance error messages with recovery guidance. E.g., 'Device not found. Try list_devices() to see active devices.' Categorize errors: retryable (timeout, transient), user-fixable (invalid MAC), fatal (auth failed).