Read one thread in full

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

Annotations already establish that this is a read-only, non-destructive operation, so the description adds useful behavioral detail beyond them: results are flattened, sorted by score, and include permalinks. It does not cover every edge case like rate limits, but the key return-shape behavior is disclosed.

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 sentences deliver the tool's purpose, output shape, and accepted input formats without repetition or filler. The most important information is front-loaded.

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 sufficiently covers what the caller gets: the post, its comments, ordering, and permalinks. Combined with the annotations and complete parameter schemas, an agent has enough context to call the tool correctly.

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?

The schema already describes all three parameters with 100% coverage. The description mostly restates the reference parameter's accepted input forms and adds no new meaning for sort or commentLimit. This matches the schema-heavy baseline.

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 states a specific verb ('Read'), a specific resource ('one thread'), and the full scope ('the post and its comments'). It clearly differentiates from sibling tools like browse_subreddit or get_subreddit_info by targeting a single thread rather than a subreddit or user activity.

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 makes the intended use case clear: retrieve a complete thread given a URL, permalink, or post id. It does not explicitly contrast with sibling tools, but the reference-based input and 'one thread' framing give a strong context for when it should be selected.

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