Document MCP behavior: agent may fall back to direct txc CLI execution

[zdeneksrejber]

Summary

This issue is documentation-oriented.

In real usage, when MCP execution has a startup/runtime problem, agents may continue by using direct txc CLI commands in terminal. That fallback behavior is already happening in practice.

Request

Please document this behavior so contributors and users understand what to expect:

1. When MCP operations fail to execute, agent workflows may use direct txc CLI as a practical fallback.
2. This is expected operational behavior for continuity, not an unexpected workaround.
3. Output/trace implications should be described (MCP result vs terminal command output).
4. Include guidance for Windows/macOS/Linux environments.

Why this matters

• Reduces confusion during troubleshooting.
• Helps maintainers and contributors interpret agent actions correctly.
• Makes the supported operational model explicit.

Suggested documentation locations

• README.md
• MCP docs / troubleshooting docs (for example in docs/)
• Any agent/MCP usage guidance

Environment context

• Observed in Windows workflows
• Applies to cross-platform usage (Windows/macOS/Linux)
• Repo: TALXIS/tools-cli