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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: result ordering and the cursor-based paging contract. It does not state access requirements (must the agent be a channel member?) or error behavior for unknown channels.

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 short sentences, zero filler, with the core operation stated first and the pagination tip second. Every clause carries information.

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 three-parameter read tool with no output schema, the description conveys ordering and that the response carries a "next" cursor, which is the key return-value detail an agent needs. Annotations cover the rest of the safety profile; only permission/error semantics are left unstated.

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 all three parameters are already documented, including the meaning of "before" and the accepted channel forms. The description repeats the cursor semantics rather than extending them (no note on cursor expiry, page size interaction, or filtering options). 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?

Specific verb and resource ("Read the top-level posts of a channel") with a stated ordering ("newest first"). The phrase "top-level posts" implicitly separates it from read_thread/read_messages, but no sibling is named, so differentiation must be inferred.

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?

Usage is implied by the resource wording, and the pagination instruction ("Pass 'next' back as 'before' for older posts") tells the agent how to continue paging. There is no explicit when-not guidance or pointer to alternatives such as read_thread for replies or read_mentions for filtered views.

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