MCP Streaming Chat

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe, read-like operation. The description adds that it uses Server-Sent Events and optional chart context, which is useful. However, it does not detail output format, error behavior, or rate limits, so it contributes some but not extensive transparency beyond annotations.

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 concise with two sentences plus an example, and the group tag is helpful. It is front-loaded with the key purpose. However, the example could be more structured or separated for clarity.

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?

Given the complexity (3 parameters, nested chart object, streaming output), the description is incomplete. It lacks details on how to handle the SSE stream, expected events, or any output schema. Important operational context is missing for an agent to correctly invoke the tool.

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?

With only 33% schema description coverage, the description should compensate, but it only provides a brief example and does not explain the 'message' or 'language' parameters beyond the schema. The optional chart parameter is hinted but not fully detailed. The description adds marginal value over the schema.

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 'Server-Sent Events streaming chat completion with optional chart context', specifying the verb (streaming chat) and resource (completion). It distinguishes this tool from siblings like 'ai_chat' by emphasizing streaming via SSE.

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 no explicit guidance on when to use this tool versus alternatives such as 'ai_chat' or other streaming tools. It lacks when-to-use or when-not-to-use conditions, leaving the agent to infer based on the name alone.

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