Stream realtime events (SSE)

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds valuable context about SSE protocol, unidirectional stream, and timeout return behavior, without contradicting 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 relatively concise (4 sentences) and front-loaded with purpose, but the first sentence redundantly restates the title. Structure is logical: purpose, protocol, client requirements, behavior, endpoint call.

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 covers streaming nature, protocol, and return behavior, but lacks details on timeout configuration, error handling, or how to close the stream. With no output schema, more context would improve completeness for an SSE 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?

Schema coverage is 100% with clear description for the single required parameter taskRunIds. The description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 tool streams realtime events (SSE) for task runs, specifying it establishes a unidirectional event stream and returns events before timeout. However, it does not explicitly differentiate from sibling streaming tools like render_subscribe_logs.

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 client guidance (setting Accept header, keeping connection open) and mentions timeout behavior, but lacks explicit instructions on when to use this tool versus alternatives like render_list_task_runs or render_subscribe_logs.

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