52 tools across network, protect, and site_manager modules. Examined source code reveals tool registration via FastMCP but critical gaps: (1) No visible input schemas in provided code, cannot verify parameter types, constraints, or descriptions. (2) Tool descriptions appear minimal or absent in the registration layer. (3) Output schemas not documented. (4) Error handling patterns not evident. Naming follows verb_noun pattern (list_devices, get_wlan, create_network, delete_route) which is correct, but definitions themselves are not visible in the provided excerpt.

• Add comprehensive input schemas to all 52 tools with typed parameters, enums for constrained values, and min/max bounds for numeric fields.
• Write 50-200 character descriptions for each tool explaining WHAT it does, WHEN to use it, and any prerequisites. Include dependency hints (e.g., 'Call list_devices first to find device IDs').
• Document output schemas showing all returned fields, types, and pagination info. Include examples of chaining IDs (e.g., device_id for downstream update calls).
• Add tool annotations: mark all read-only tools with readOnlyHint=true, destructive tools with destructiveHint=true, and idempotent tools with idempotentHint=true.
• Implement confirmation or dry-run patterns for all 6 delete_* tools. Return 'Would delete X. Call confirm_delete(id) to proceed' or similar.

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

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