Send chat message as bot

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false. The description contributes one genuinely useful behavioral fact not in the annotations: the message is publicly visible to everyone in chat, which rules out a private/whisper interpretation. It says nothing about rate limits, required bot presence, or moderation filters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action, with no filler. The second sentence is somewhat redundant with "chat" in the first, but it does carry the visibility information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter messaging tool with full schema coverage and no output schema, the description covers the essentials. Minor gaps remain around prerequisites (bot joined, permissions) and rate limiting, but nothing that would cause an agent to call it incorrectly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already documents both the optional channel default (SE_CHANNEL_ID/token owner) and the message constraints. The description's only parameter-adjacent signal is "the channel's chat," which adds nothing beyond what the schema states. Baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Send a message to the channel's chat") plus the acting identity ("as the StreamElements bot"). It is clearly distinguishable from the other bot_* siblings (join, leave, mute, unmute, set_language, get), though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given. It does not say whether the bot must already be joined to the channel, whether this is for public announcements only versus whispers/DMs, or how it relates to siblings like bot_join.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.