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

With no annotations, the description carries the burden well: it discloses that providing only one of forumName/subForumName is rejected, that sort=HOT may return an empty page, that sort must be HOT or LATEST, and that content is truncated. It does not discuss permissions/rate limits or pagination bounds, but the behavioral picture is solid.

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 what the tool is, then the routing rules; each sentence carries actionable content. The parenthetical about the news-digest board and late-2025-to-early-2026 coverage is mildly incidental but still frames content expectations.

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 list tool with no output schema and no annotations, the description covers selection rules, sort semantics, the board-pairing constraint, and the truncation/next-step behavior. Pagination limits live in the schema, so the remaining gap is minor.

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 the baseline is 3, but the description adds real meaning beyond the schema: the coupling rule between forumName and subForumName, the semantic difference between HOT (engagement-ranked over a recent window, may be empty) and LATEST (default), and the truncation caveat with a pointer to get_article.

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 (list) and resource (published articles) and situates it in a specific corpus (Traditional Chinese zh-TW PTT-style forum), which clearly separates it from get_article and the mutation siblings. An agent can identify the tool's scope without opening the 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?

Explicitly routes the agent: use forumName+subForumName together to list a board, otherwise use sort=HOT for trending or omit sort/sort=LATEST for recent, and it names get_article as the follow-up for full content. The rejection condition for partial board params is stated outright.

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