Queue

Most tools target distinct sub-resources, but there is real overlap: evaluate_plan_coverage and evaluate_support_promise both 'decide whether' something is in the approved set, differing only in plan-coverage vs exact-wording, and get_queue_context vs search_customer_plans both retrieve customer plans. The descriptions do clarify these boundaries, but an agent could still easily confuse the two evaluate gates.

Every tool follows a clean snake_case verb_noun pattern (create_/evaluate_/get_/list_/save_/search_ + noun), with consistent grouping of the list_* and save_* families. No convention mixing anywhere.

13 tools is well within a reasonable range for a plan/approval domain. It is slightly granular with four list_* and four save_* tools, but each maps to a distinct sub-resource (windows, channels, staffing, catalogs) rather than being redundant.

The surface covers the read/evaluate/save lifecycle well, with save_* handling both create and revise. The notable gap is deletion: there is no way to remove a customer plan, catalog, or saved channel/window/promise, so lifecycle coverage is incomplete at the teardown end.