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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. However, the description adds nothing about the behavior that matters most here: that this is a streaming endpoint — long-lived connection, event/polling semantics, termination, or auth requirements are all undisclosed.

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?

It is short, but the route string is duplicated verbatim and the only other clause is metadata about the operation ID and a pointer to describe_operation. Almost none of the text conveys meaning about the tool's purpose.

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?

For a streaming tool with a nested query object, zero parameter documentation, and no output schema, the definition leaves the agent without enough information to invoke it correctly — neither the streaming behavior nor the parameters are explained.

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 there are two parameters (a free-form query object and params.id). The description says nothing about the id's format, scope, or what the query object accepts, so it does not compensate for the schema gap at all.

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 only restates the HTTP route twice ("GET /api/review/runs/:id/stream") without saying what a review run stream is, what it streams, or how it differs from the sibling get_review_runs_by_id_3a1c2f7126c2e556c467d4a7 or get_review_entries. It is effectively a tautology of the tool name.

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 when-to-use or when-not-to-use guidance is given. The only actionable hint is that describe_operation provides native request schemas, which implies the agent should inspect that sibling first, but the choice between this streaming endpoint and the plain run-fetch sibling is never addressed.

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