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

readOnlyHint=true already tells the agent this is a safe read, and the description reinforces the required inputs and names the underlying GET endpoint. It adds no detail on pagination behavior, result caps, or why a "stream_"-named tool returns a paged GET result rather than a live feed, which is a real ambiguity left unaddressed.

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?

Three short sentences with the operation first, the prerequisite second, and a concrete example plus endpoint last. Nothing is redundant and nothing is buried.

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, fully-schema-documented list tool with no output schema, the description covers the operation, required inputs, filtering, and the backing endpoint. Only the ambiguous streaming-vs-paged behavior and result semantics remain unexplained.

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 every parameter (id, type, filter, sort, limit, offset) is already documented in the schema, including examples. The description quotes a filter example that duplicates the schema's own text, adding no meaning beyond it.

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?

States a specific verb and resource ("List/filter the members of one channel") and scopes it to a single channel, which separates it from stream_query_channels and stream_query_users. It does not explicitly name or contrast a sibling, so it falls short of the top mark.

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 states a prerequisite ("Requires the channel type + id") and the intended operation, so usage is implied. It gives no explicit when-to-use vs when-not guidance and never mentions an alternative tool for broader member or user lookups.

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