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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds valuable context the annotations do not: the exact return shape (compact Markdown) and that trust levels are embedded per author. It stops short of noting size limits, pagination behavior, or what happens with an invalid ref.

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 zero waste, and the most important information — what is returned — is front-loaded before the optional-parameter tip.

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?

With no output schema, the description correctly compensates by describing the return format and included metadata. For a simple two-parameter read tool this is nearly complete; only error/edge behavior for a malformed ref or very large threads is unaddressed.

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 100%, so both ref and after are already documented in the schema. The description's note that after fetches 'only newer posts' largely restates 'Only posts after this id' and adds no format or edge-case detail, so the baseline 3 applies.

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?

The description names the resource (a whole thread) and, unusually, the return format (compact Markdown with each author's trust level), so an agent knows exactly what comes back. It does not explicitly contrast with siblings like list_threads or search, so it falls short of full sibling differentiation.

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 only usage guidance is incremental fetching with after=<post id>; nothing explains when to read a thread versus listing or searching threads. The implied core use case (fetch a thread's content) is clear enough from the resource name, but exclusions and alternatives are absent.

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