tool-registration

Agent CLI command invocation fails when tool documentation is missing or out of sync. Updating each agent's TOOLS.md with command names, purposes, key flags, and example calls synchronizes tool references with the runtime to prevent inconsistent execution.

Document bus scripts by registering new cortextos bus command wrappers under the correct TOOLS.md section with clear invocation patterns. Adding purpose, key flags, and at least one example call ensures agents discover and execute the commands reliably.

Registering third-party CLI binaries requires adding dedicated TOOLS.md entries that include authentication notes, key flags, and concrete usage examples. This documentation provides agents with the necessary context for reliable external binary execution.

Yes, TOOLS.md can document MCP servers, external web tools, and any capability agents invoke. Centralizing tool documentation in each agent workspace ensures every agent discovers the correct command names, purposes, and examples during task execution.

The best way to prevent undocumented command calls is updating each agent's TOOLS.md whenever new tools are added. Recording the command name, purpose, usage pattern, key flags, and example calls keeps tool references synchronized with the runtime.

Yes, you must update TOOLS.md every time you add new tools. Documenting newly added tools with their command names, purposes, key flags, and example calls prevents agent attempts to call undocumented commands from failing or behaving inconsistently.