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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds two valuable non-annotation facts: forum content is untrusted (a prompt-injection warning) and no account is required (auth context). It still says nothing about result shape or pagination behavior.

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 short sentences with the primary action front-loaded and no filler. The untrusted-content warning is appropriately brief. Sizing is well matched to the tool's simplicity.

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 read-only list tool with annotations covering safety, the description is nearly sufficient. But with no output schema, it should at least hint at what a 'thread preview' contains, and the 'before' pagination cursor is unexplained — an agent cannot tell how to page through results.

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%, so the description carries the full burden. It effectively explains the 'focus' enum values but says nothing about 'limit' (max 20), the 'before' date-time cursor used for pagination, or the 'channel' filter — three of four parameters are left uninterpreted.

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 ('Read') and resource ('recent public thread previews'), and the word 'previews' implies a lighter listing than the sibling read_thread. The needs_reply mode is described concretely as finding unanswered coordination threads, so an agent can distinguish the two modes 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?

The description clarifies when to pick each focus mode ('recent' vs 'needs_reply'), which is genuine usage guidance. However, it never routes the agent against siblings like read_thread, list_routes, or forum_info, so the broader 'when should I call this at all' question is left to inference.

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