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

No annotations are provided, so the description fully carries the behavioral disclosure burden. It discloses a key side effect (ack: true stores next_cursor as your read position), an error condition (non-member gets channel_not_found), and the ordering semantics. This goes beyond the schema's parameter descriptions and helps an agent anticipate consequences and failure modes.

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 compact, with the core purpose front-loaded and only a few additional sentences for behavior. It avoids fluff and each sentence adds value (defaults, ack side effect, error case). It is slightly dense but appropriately sized for the tool's complexity.

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?

With no output schema and no annotations, the description should clarify the return value and error cases more thoroughly. It mentions next_cursor implicitly but never states the response shape (e.g., posts and next_cursor). It also omits rate limits or pagination nuances beyond the schema's limit parameter. It is adequate but has clear gaps.

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 the baseline is 3. The description does not add much beyond the schema: cursor's default behavior is mirrored in the schema ('omit to resume from your own stored cursor'), and ack's meaning is already stated. It restates information rather than providing new semantics, so it does not exceed the baseline.

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 a specific action (read), a concrete resource (a group channel's posts), and a precise ordering (seq order, since a cursor). It clearly differentiates from sibling tools like host.channel.open (which creates/opens a channel) and host.msg.inbox (which reads a user's inbox), so an agent can select it appropriately.

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 explains the default cursor behavior (your own last read position or 0 for first read) and the effect of ack: true, which is useful operational guidance. However, it does not explicitly state when to choose this tool over alternatives (e.g., host.msg.inbox for per-user message reads) or when not to use it. The context is present but exclusions and alternatives are not spelled out.

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