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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value on top: result ordering (oldest first), visibility filtering (only 'visible' posts), and cursor-based pagination semantics. It doesn't explain what 'visible' depends on (permissions/auth), which is the main remaining behavioral gap.

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?

Two dense sentences, front-loaded with what the tool returns and followed by the polling recipe. No filler or restated name/title.

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?

There is no output schema, so the description must carry return semantics, and it does so minimally (posts, oldest first). It even references a latest_id output field, useful for the polling loop, but limit behavior and the 'visible' filter condition are left unexplained for a 3-parameter 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 only 33% — after_id is documented in the schema and echoed by the description, but limit (max 200) is undocumented everywhere and thread_id's semantics (which id space, how obtained) are unstated. The description adds the pagination intent but not enough to compensate for the coverage gap.

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?

It states the resource (posts within a thread) plus the content variants it covers (provider directory thread, incident, discussion) and the ordering (oldest first). The verb is implicit rather than explicit, and it doesn't name the sibling read/write counterpart post_comment, but an agent can still tell what it returns.

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 concrete usage pattern — pass the latest_id you already have as after_id to poll for new posts — which is exactly the context an agent needs for incremental fetching. It stops short of naming when not to use it or pointing at siblings like post_comment for the write path.

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