ToolRoute

The two tools occupy clearly separate phases of a single workflow: register_tools creates a stable set_id, route_tools consumes it to rank tools for a query. Descriptions explicitly cross-reference each other (set_id comes from register_tools), so an agent cannot reasonably confuse them.

Both names follow the same verb_noun pattern (register_tools, route_tools) with consistent snake_case and plural noun form. Predictable and readable.

Only two tools, but they map exactly to the domain's two-step lifecycle (register a set, then query it), so each earns its place. It is on the thin side for a routing service that could plausibly need set inspection or cleanup operations.

The core register-then-route flow is covered, and idempotent set_id generation partly mitigates losing a set_id. However, there is no way to list, inspect, refresh, or delete registered sets, leaving agents without cleanup or discovery operations once state accumulates over the 90-day retention window.