Toolset Selection for Production Rocky

Rocky works best when the available tools match the task. Too few tools create fake certainty; too many tools expand the safety surface without improving the result.

Official Hermes Agent docs: https://hermes-agent.nousresearch.com/docs/reference/tools-reference

Core selection pattern

• Use file and terminal tools for owned code and local verification.
• Use web tools for current public facts and official docs.
• Use browser or computer-use tools when visual UI behavior matters.
• Use image generation only when the configured provider and brand direction are acceptable.
• Use memory and skills for durable preferences and procedures, not one-off task status.

Production checklist

• List the task class before enabling optional tools.
• Confirm tools that need credentials are actually configured.
• Keep destructive or high-trust tools out of public-facing unattended jobs unless the scope is narrow.
• For public wiki expansion, restrict edits to public data and assets.
• Document tool failures and switch strategies rather than pretending the tool worked.

Pitfalls

• Using a browser when a direct HTTP or file check would be more reliable.
• Using web search for private project truth instead of the source file.
• Enabling unrelated admin tools for simple content work.
• Forgetting that tool changes may require a new session to take effect.

Verification steps

• Run a small probe with the chosen tool before relying on it.
• Check output from the original source, not just an extracted summary.
• For generated assets, inspect the actual pixels before publishing.
• For code changes, run the relevant syntax, unit, route, or visual checks.