Description

The message tool description shown to the LLM only lists supported actions for the current session channel (e.g. Telegram), not for all configured channels. For example:

Current channel (telegram) supports: delete, edit, react, send, topic-create.

This means isolated cron agents that need to use Discord-specific actions like read or search have no way of knowing these actions exist — they only see the Telegram action list.

Impact

A cron job that previously worked (reading Discord messages via action: "read") broke because the isolated agent saw only Telegram actions in the tool description and concluded read was not available.

Expected Behavior

The tool description should list supported actions per configured channel, e.g.:

Supported actions:
- telegram: delete, edit, react, send, topic-create
- discord: delete, edit, poll, pin, react, read, search, send, thread-create, ...

Or at minimum, when an isolated agent has access to multiple channels, all available actions across channels should be listed.

Workaround

Explicitly mention available actions in the cron job prompt text.

Environment

• OpenClaw version: 2026.2.15
• Channels: Telegram + Discord
• Observed in: isolated cron agent sessions (sessionTarget: "isolated", payload.kind: "agentTurn")