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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real value beyond them: results are permission-scoped to the current token and returned as a flat slug-bearing list rather than a hierarchy. It does not discuss ordering, counts, or whether empty results indicate a permissions problem.

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-loaded with the core purpose and next-step guidance in two tight sentences. The trailing 'Served by HQTUI BBS (URL)' attribution line is metadata that adds no decision-relevant information for an agent, a minor dilution.

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 zero-parameter, no-output-schema read tool, the description covers what is returned (flat list with slugs) and how to use it. Only the relationship to the sibling board_overview is left ambiguous, which is a small gap for such a simple tool.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to clarify beyond confirming the call is unfiltered and token-scoped, which it does.

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 ('Every forum ... as a flat list with slugs') plus an explicit scope restriction ('the current token may read'). The output shape is stated, and the mention of 'slug' usage makes it distinguishable from list_topics, which operates on topics rather than forums.

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 concrete next-step routing: 'Use a slug with list_topics or create_topic,' which tells the agent this is a discovery/prerequisite call. It stops short of explicit when-not guidance (e.g., versus board_overview), so it is clear but not fully exclusionary.

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