Send a chat message

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

The description accurately reflects the write operation and adds key behavioral details (prerequisites, bot vs streamer identity). Annotations already indicate non-readonly and open world, so no contradiction.

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 sentences, no filler. Purpose and key usage details are front-loaded.

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 write tool, the description covers all necessary context: prerequisites, parameter options, and behavioral choice. Lacks error or rate limit info, which is acceptable.

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% with good descriptions. The description adds extra clarity for 'as_streamer' but does not significantly improve upon the schema for 'platform' and 'message'.

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 action (post), resource (message), and context (live chat via Lumia bot). It distinguishes from other chat-related tools like 'send_announcement' or 'speak'.

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 provides prerequisites (platform connected, chatbot enabled) and clarifies the 'as_streamer' parameter. It does not explicitly list alternatives but the context is sufficient.

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