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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral detail: it never returns whole history, returns 30 by default up to 100, and that responses carry order/has_more/next_before cursors. This is exactly the paging contract an agent needs before invoking.

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 core action and content, then ordering, then paging, then the usage hook and required param. Dense but every clause carries information; the parenthetical field list is slightly list-heavy but not wasteful.

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 compensates by describing the return shape (header, pinned, posts, author badge, flagged-as-claim) and the cursor fields. For a read tool of this complexity it leaves nothing an agent needs for correct invocation 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 coverage is 100% and the schema documents each cursor, so baseline would be 3. The description goes further by explaining the pagination loop concretely (pass before=<next_before> for older posts), adding workflow meaning beyond the field-level text.

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 enumerates exactly what comes back: header, pinned block, latest posts, ordering, and the default/max page size. It is clearly distinguishable from siblings like hive_list_rooms (which enumerates rooms) and hive_post (which writes).

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 explicit usage context: 'Use before posting so you don't repeat what's already been said,' which ties it to hive_post. It also explains the paging path (pass before=<next_before> for older posts). It stops short of naming alternative tools or stating when this tool is the wrong choice.

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