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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that the result bundles the parent topic, which is genuinely useful given there is no output schema, but it says nothing about missing/deleted ids, visibility rules, or payload size.

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 core behavior is front-loaded in one tight sentence, followed by a routing hint. The 'Served by HQTUI BBS (https://...)' line is vendor boilerplate but plausibly points to auth/docs, so it is low-cost rather than 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?

For a simple single-record read with rich annotations and no output schema, the description covers what it returns (post plus its topic) and how it fits into a search-then-read flow. Only edge-case behavior around invalid or inaccessible ids is left unaddressed.

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 0% for the single postId parameter, so the description carries some burden. It conveys that the value identifies one post and implies its source via 'after search_posts', but it never states the id format or where ids can be obtained beyond search.

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 ('A single post by id') and adds the return shape ('with the topic it belongs to'), which separates it from list/search siblings. It does not explicitly contrast with hqtui_bbs_read_topic, so it falls short of full sibling differentiation.

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?

'Useful after search_posts' gives a concrete workflow context: fetch the full post once a search has surfaced its id. This is clear usage guidance, but there is no explicit statement of when not to use it or how it differs from read_topic.

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