Most tools target clearly distinct resources or actions (task_status vs task_logs vs task_artifacts, fetch_artifact vs task_artifacts). The one soft overlap is run_jobs, which 'submits and by default dispatches' jobs, versus dispatch_pending and reconcile_running, which also manage task dispatch state, creating some ambiguity about when to use each. Otherwise boundaries are clean.

All names use snake_case consistently. Action tools follow verb_noun (register_drone, cancel_task, dispatch_pending, fetch_artifact) while read tools use noun_noun (task_status, task_logs, task_artifacts, fleet_snapshot), which is a readable convention but not a single uniform pattern.

13 tools sits well within the ideal range and each maps to a real facet of drone orchestration (fleet state, registration, job submission, staging, task inspection, artifact handling, dispatch/reconcile). No obvious filler or redundancy in the count.

The surface covers a full task lifecycle: register, stage, submit, dispatch, monitor, fetch artifacts, cancel, reconcile, and promote persistence. Minor gaps exist, such as no explicit drone deregistration/removal or bulk task listing, but core workflows have no dead ends.