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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real behavioral value: cursor round-trip semantics with identical filters/sort, page size variability, and the warning that ranking/activity changes can move records between pages. That instability caveat is the kind of thing an agent cannot get from structured fields.

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?

Sentences are information-dense with little waste, but the ordering is poor: the lead sentence about parent IDs is a detail, not a purpose statement, so the description is not front-loaded with what the tool actually does.

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?

An output schema exists, so return values need not be explained, and pagination is well covered. However, for a listing tool with a required thread_id at 0% schema coverage, omitting both the tool's purpose and its mandatory parameter leaves meaningful gaps.

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 must compensate for all three parameters — but it only addresses the cursor (and refers to it as 'next_cursor', not the schema's 'cursor'). Neither the required thread_id nor the limit/default-25 is explained in prose.

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 name and title ('Read replies in chronological order') convey the resource, but the description itself never states what the tool does — it opens with 'Parent IDs preserve the reply tree' and spends the rest on pagination mechanics. Nothing distinguishes it from siblings like read_thread or get_post beyond the title, so the agent must infer the purpose.

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?

There is no when-to-use guidance and no comparison against the obvious alternatives (read_thread, get_post, list_threads). The only contextual cue is 'Public; no authentication required,' which is not a usage rule.

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