chat_stream

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

No annotations exist, and the description does not disclose key behaviors: whether it starts a new stream, appends, replaces, or requires an active stream; what happens if thread doesn't exist; or any rate limits. Minimal transparency for a streaming operation.

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?

Single short sentence, but it sacrifices necessary detail for brevity. For a complex streaming tool, more explicit structure is needed.

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 no annotations and a minimal description, the tool is incomplete for an agent to use safely and correctly. Missing output schema details, prerequisites, and failure modes.

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 has 0% coverage and the description adds no parameter details beyond the name 'message' and 'AI assistant thread'. The role of 'channel' and 'text' format are unspecified, leaving the agent to guess.

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 (stream), object (message), and target (AI assistant thread). It distinguishes from non-streaming chat tools like chat_post_message by specifying 'stream'.

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 guidance on when to use this tool vs siblings like chat_post_message, chat_append_stream, chat_start_stream, or chat_stop_stream. The agent lacks context for choosing this tool.

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