MCP Tool-Call Stream

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description's brief mention of SSE-stream does not contradict and adds minimal context. The description does not elaborate on stream behavior (e.g., event types, termination), which is acceptable given annotation completeness.

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 very short (two lines), which is concise but at the expense of clarity. It could include more useful information without being verbose. The group label adds some structure but is not fully earned.

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 tool is a streaming endpoint with three parameters and no output schema, the description is incomplete. It does not explain the streaming mechanics, expected output format, or any usage constraints, making it insufficient for proper agent invocation.

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 description coverage is 0%, and the description does not mention any of the three parameters (tool, args, language). The agent must rely solely on the schema, which lacks descriptions for 'tool' and 'args'. This is a critical gap.

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 states 'SSE-stream of a tool call envelope', which indicates a specific resource and action, but uses jargon that may be unclear to an agent. It differentiates from siblings by being a generic streaming tool, but the purpose is somewhat vague.

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 given on when to use this tool versus alternatives. It mentions 'Group: MCP Advanced' but does not provide context on scenarios or exclusions, leaving the agent to infer usage from the name alone.

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