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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely new context the annotations cannot convey: results are aggregated across multiple surfaces (preview link, approval link, app/agents) and include replies plus counts. It does not mention pagination or ordering, which is a minor 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 tight sentences, with the scope front-loaded before the disambiguation from list_comments. The middle clause is a dense list that reads as a fragment, but nothing is wasted.

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 two-parameter read tool with no output schema, the description supplies enough: what is returned (threads with replies and counts), where from, and what the status filter means. Pagination/ordering behavior is the only notable omission.

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% and both parameters are already documented there, including the enum values and the 'open = not resolved' meaning. The description largely restates the status semantics rather than adding format or interaction detail, so baseline 3 is appropriate.

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 ('comment threads on one post') and enumerates the sources those threads come from (preview link, approval link, team in the app, agents). It explicitly names the sibling list_comments and explains how it differs, so an agent can separate the two without opening a 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 gives a clear exclusion ('not comments people left on the platforms (that is list_comments)') and explains the status semantics, which guides selection. It does not, however, spell out when in a workflow an agent should reach for review comments versus, say, get_post or preview_post.

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