Aether-X Port Delay Intelligence

At least six tools (get_port_risk, get_port_congestion_risk, get_port_operations_status, get_port_state, get_port_trend, get_public_port_feed) all answer 'is this port congested/delayed?', differing mainly in framing (free vs paid, observation vs inference) rather than target. The presence of five deprecated duplicates compounds the risk of misselection, even though descriptions try hard to steer the LLM with 'CRITICAL INSTRUCTION' hints.

Names are overwhelmingly snake_case with a predictable verb_noun shape (get_*, evaluate_*, list_*, forecast_*, assess_*, request_*). The verb set varies (get vs evaluate vs assess for similar reads), but the convention itself is consistent and readable.

26 tools is heavy for this scope, and five of them are explicit DEPRECATED aliases (evaluate_scdew_warning, get_cdr_risk, get_irdi_index, get_pci_index, predict_vessel_queue) that pad the surface without adding capability. The count would be near-appropriate (~20) after pruning the duplicates and the no-description list_supported_ports placeholder.

Coverage spans the domain well: port-level signals, multi-port comparison, chokepoints, corridors, inland rail/truck, forecasting, fiscal routing, shipment reconstruction, and M2M key issuance. Gaps are minor (per-vessel IMO/MMSI tracking is explicitly declined, list_supported_ports lacks a description), none of which creates a hard dead end.