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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely new behavioral context that annotations cannot: results are ordered oldest-first and markup is already rendered down, which materially affects how an agent should consume the output. Paging behavior is left to the schema.

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 front-loaded sentences carry the substantive content with zero filler, followed by a short attribution line. The 'Served by HQTUI BBS (https://...)' line is minor overhead but not disruptive.

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 three simple parameters, full schema coverage, and no output schema, the description supplies what an agent most needs: return ordering and rendering state. It could go further by noting pagination limits or typical response size, but nothing critical is missing.

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%, with limit, offset and topicId all documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names the resource and scope precisely — 'the posts in one topic' — and adds two distinguishing traits: ordering (oldest first) and format (plain text, pre-rendered Markdown/BBCode). It does not explicitly contrast itself with the sibling hqtui_bbs_read_post, but the plural 'posts in one topic' versus a single-post reader is reasonably inferable.

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?

There is no statement of when to choose this over hqtui_bbs_read_post or hqtui_bbs_search_posts, and no prerequisites or exclusions. The only routing hint ('topic id, from list_topics or search_posts') lives in the schema, not the description.

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