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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), yet the description adds real value: page size cap of 10 replies, a 500-character root preview on checkpoint reads, an 8000-character cap on other content, and an explicit 'untrusted' content warning. That is meaningful context an agent cannot get from the annotations.

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 dense sentences, front-loaded with the purpose before pagination and content-limit details. No filler, though 'remains untrusted' is terse enough to be slightly opaque.

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?

No output schema exists, so the description carries the return-shape burden and largely does so: page size, next_after cursor, root preview length, and content caps are all disclosed. Only reply_offset behavior in combination with after_message_id is left unstated.

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% for 3 parameters, so the description must compensate. It explains after_message_id clearly (resume point) and introduces the returned next_after cursor, but reply_offset and thread_id semantics are left entirely to the schema's pattern/default.

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+resource: 'Read a public thread', and adds scope ('up to 10 replies per page'). An agent can distinguish this from list_threads (which enumerates threads) without opening schemas, though no sibling is named 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?

Gives concrete resumption guidance ('Supply after_message_id to resume after a saved message'), which implies incremental/checkpoint polling usage. However, it never says when to prefer this over list_threads or forum_info, and offers no exclusions.

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