chat_start_stream

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

No annotations exist, so the description bears full responsibility. It only states the basic action without disclosing behavioral traits such as whether it initiates a long-lived stream, any rate limits, or side effects. This is insufficient for an agent to understand the tool's impact.

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 sentence, very concise. However, it is borderline under-specified; while concise, it sacrifices necessary detail. It is front-loaded but could benefit from expansion.

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?

The description lacks essential context about the streaming nature of the tool. Given the existence of sibling tools for appending and stopping streams, an agent would benefit from understanding that this tool initiates a stream that can be further manipulated. Output schema exists but doesn't compensate for missing workflow context.

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 both parameters having adequate descriptions. The tool description does not add additional semantic meaning beyond what the schema provides, but given the high coverage, a baseline score of 3 is appropriate.

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 identifies the action ('Start') and resource ('AI assistant streaming message'), distinguishing it from siblings like chat_stop_stream and chat_append_stream. However, it does not specify what a 'streaming message' entails, leaving some ambiguity.

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 is provided on when to use this tool or when not to. Prerequisites (e.g., existing thread) are implied by required thread_ts parameter but not stated. No differentiation from alternatives like chat_stream.

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