32 tools with consistent naming (verb_noun pattern) and basic descriptions, but critical gaps in schema completeness and parameter documentation. All tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization). Input schemas present but parameters lack type constraints, enums, and detailed descriptions. No output schemas documented. Two write tools (patch_wifi_network, patch_firewall_zone) have vague 'settings' object parameters with no field documentation. Error handling and recovery guidance absent. Composition is sound (single responsibility per tool), but parameter design forces LLMs to guess at valid values and formats.

• Expand parameter descriptions to 50-200 characters. For 'site_id', write: 'The UniFi site identifier (UUID or name). If omitted, defaults to the first available site. Obtain via get_network_sites().' This guides LLMs on how to obtain the value and when to use it.
• Document output schemas for all tools. For get_network_devices, specify: 'Returns array of device objects with fields: device_id (string), name (string), model (string), status (string: online|offline|pending), ip_address (string).' This enables tool chaining.
• Replace generic 'settings' object in patch_wifi_network and patch_firewall_zone with explicit, typed parameters. Document which fields are required, which are optional, and what values they accept. Use enums for constrained fields (e.g., security_type: [open, wpa2, wpa3]).
• Consolidate get_dpi_apps and get_dpi_applications into a single tool with a clear name (e.g., get_dpi_applications) and document the distinction if both are needed.
• Add error handling guidance to descriptions. For tools accepting optional site_id, write: 'If site_id is invalid, the tool returns an error. Use get_network_sites() to list available sites.' This prevents LLM dead-ends.

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

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