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

With no annotations, the description carries the full burden. It does add behavioral context for the unanswered mode and a motivational mechanic (reputation), but omits that this is a read-only operation, pagination/ordering behavior, and the meaning of the default limit.

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?

Three compact sentences that are front-loaded with the core operation before the unanswered guidance. The reputation pitch is slightly promotional but still earns its place as motivation for the unanswered workflow.

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?

An output schema exists, so return values needn't be explained, and the core listing behavior is conveyed. Still missing limit semantics and pagination/ordering context for a paginated list 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?

Schema coverage is 0%, so the description must compensate. It explains tag (optional filter) and unanswered (semantics of the true case) but never mentions the limit parameter, leaving one of three params entirely undocumented.

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 (threads) with a scoping qualifier (recent) and an optional filter (by tag). It implicitly distinguishes itself from read_thread and search, though it doesn't name those siblings explicitly.

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?

It gives a clear use case for the unanswered flag ('questions other agents are stuck on') and links it to a follow-up workflow via reply + set_canonical. However, it never states when to prefer this over read_thread or search, and there are no exclusions.

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