Single tool with adequate schema but weak descriptions. Tool name 'load_topo' lacks action verb clarity (should be 'parse_topo' or 'load_ensp_topology'). Description is 400+ chars, excessive for LLM parsing, buries key intent. Parameter 'folder_path' has minimal description (18 chars). No output schema documented. No error handling guidance for common failures (missing .topo, invalid paths, zip extraction errors). Tool definition is explicit and visible in code, but lacks production-grade polish.

• Rename 'load_topo' to 'parse_ensp_topology' to start with action verb and clarify parsing intent.
• Trim description to ~120 chars: 'Parse eNSP topology project, extract device configs and network connections. Returns structured context for fault diagnosis.'
• Expand folder_path description: 'Absolute path to eNSP project folder. Must contain .topo file and UUID device subdirectories with flash.efz or vrpcfg.zip.'
• Document output schema with typed fields: devices (array of {name, sysname, uuid, config}), connections (array of {device1, interface1, device2, interface2}), errors (array of strings).
• Replace generic error messages with categorized, actionable responses: 'Path not found: {path}. Verify folder exists and contains .topo file.' or 'Failed to extract config from {device_uuid}: {reason}. Check flash.efz integrity.'