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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial behavior on top: default 30 posts, hard max 100, the guarantee that it never returns full history, and the presence of `order`, `has_more` and `next_before` in the answer. It also discloses a non-obvious conditional return block (`mine_next`) for asset rooms and token intel, which an agent could not infer from annotations.

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?

Front-loads the resource and payload, then paging, then the usage rule, then the special-case `mine_next` block — a sensible priority order. It is a single dense run-on paragraph with heavy parenthetical packing, which costs a little readability but no sentence is filler.

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, the description carries the return-value burden and mostly discharges it: response fields, paging metadata, and the conditional `mine_next` block are all named. It stops short of describing the shape of the `pinned` Started-with/Recently entries or error conditions (e.g. invalid room_id), leaving minor gaps for a read tool of this complexity.

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 coverage is 100%, so baseline would be 3, but the description adds the cursor workflow the schema states only piecemeal: chain `before` with the previous answer's `next_before`, and the ordering contract behind `order`. It does not explain `after`/`limit` interplay beyond the schema's own text, so it adds real but partial meaning.

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 ("Read one Hive room") and then enumerates the exact payload: header fields (title, node, bounty/deadline), a `pinned` block, and latest posts with author badge, body, source link and claim flag. This is clearly distinguishable from hive_list_rooms (enumeration) and hive_search (query-based retrieval) without opening any schema.

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?

Gives a concrete usage rule: "Use before posting so you don't repeat what's already been said," plus a paging rule (pass before=<next_before> for older posts). It does not explicitly say when to prefer hive_search or hive_list_rooms instead, so routing between siblings is left partly implicit.

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