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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, covering the safety profile. The description adds useful context (interactive overview with statuses, pagination, and builder links), but discloses no auth requirements, return format beyond links, or navigation behavior.

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?

Two tight sentences, the primary purpose front-loaded and the sibling relationship stated second. No filler, though the second sentence introduces slight tension with the first rather than fully resolving it.

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 read-only tool with a full-coverage schema and annotations carrying the safety profile, the description covers purpose, content, and the sibling relationship adequately. It could clarify whether this is a UI-only view versus a data endpoint, but no critical invocation detail is missing.

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 100%, so page and per_page are already documented with defaults and range. The description only alludes to 'pagination' and adds no syntax or semantics beyond the schema; baseline 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 names a specific verb and resource ('Open an interactive overview of your Upstream streams') and lists what the view contains (statuses, pagination, links). It also relates itself to a sibling by noting it returns 'the same account-scoped data as list_streams.' The split between 'open an overview' (UI-like) and 'returns data' leaves the exact nature slightly ambiguous, so it falls short of a clean 5.

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?

It references list_streams as an equivalent-data alternative, which hints at a routing decision, but never states when to prefer this tool over that one or over get_stream. Usage is implied rather than instructed.

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