Finding
Hermes tool choice often happens too late, after the agent has already reached for a broad default toolset instead of deliberately selecting the smallest correct capability set for the job.
Current
A typical Hermes installation has many powerful tools available at once: web search, browser automation, terminal, files, memory, session search, cron, delegation, and MCP integrations. The weak point is not lack of tools; it is unclear routing discipline before work begins. Without an explicit toolset decision, agents may use browser when web extraction is enough, terminal when a file tool is safer, delegation when a direct lookup would do, or full tool access in cron jobs that only need one capability.
Suggested
- Add a preflight tool-routing checklist before complex work. Exact change: Add a “Toolset Cartographer preflight” section to
SOUL.mdor the main operator runbook with this sequence: classify the task as lookup, file inspection, code execution, research, recurring monitoring, or multi-agent analysis; then name the minimal Hermes toolsets needed before the first tool call. - Restrict recurring jobs to minimal toolsets. Exact change: Patch every Hermes cron prompt or cron definition that performs monitoring or reporting to include an
enabled_toolsetslist, such as["web"]for web-only monitoring,["session_search"]for session review, or["cronjob"]only for cron administration tasks. - Create a tool-choice verification habit for research and build tasks. Exact change: Add one line to the relevant research or build skill: “Before acting, state the selected Hermes toolsets and why heavier tools such as browser, terminal, delegation, or MCP are not needed unless explicitly triggered by evidence.”
Impact
This makes Hermes faster, cheaper, and safer by reducing accidental overuse of broad or high-risk tools. It also improves reliability because each task begins with the right operating mode instead of drifting between capabilities. Over time, tool selection becomes a visible maturity signal: the installation knows when to search, when to inspect local files, when to delegate, when to schedule, and when not to escalate.
Effort
Small — this is mostly a prompt, skill, and cron hygiene change, not a new system. The largest effort is reviewing existing recurring jobs and adding explicit enabled_toolsets where the scope is already clear.
Public page note
Safe public content includes the operational principle, generic Hermes toolset examples, maturity checklist language, and non-sensitive routing rules. Internal-only content includes private cron prompts, raw session excerpts, exact local paths containing sensitive material, credentials, environment values, live dashboard data, and any tool output from private installations.