Set a chat mode

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

The description states the tool turns modes on/off, which aligns with the non-readOnly annotation. However, it does not disclose additional behavioral traits such as permission requirements, rate limits, side effects on other settings, or the immediate effect of changes. For a mutation tool with openWorldHint, more context is needed.

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?

The description is a single concise sentence (18 words) that is front-loaded with the primary action. Every word is necessary; no redundancy or fluff.

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?

With three parameters and no output schema, the description covers the basic action but lacks details on return values, error conditions, or the effect of the duration parameter. Given the tool's complexity (toggling modes with optional duration), additional context would help the agent.

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 coverage is 100%, so the description adds no new meaning beyond the schema. It merely lists the mode enums. The duration parameter's behavior is partially explained in the schema, and the description does not clarify its usage for different modes or provide examples.

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?

The description clearly states the tool turns a Twitch chat mode on or off, listing the specific modes (slow, subscriber, follower, emote). It uses a specific verb ('turn on or off') and identifies the resource ('chat mode'), distinguishing it from sibling tools like send_chat_message or clear_chat.

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?

The description implies usage for toggling chat modes but does not provide explicit guidance on when to use this tool versus alternatives (e.g., when to use clear_chat, send_chat_message, or other chat-related tools). No exclusions or conditions are mentioned.

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