Read chat thread

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about what the tool returns—thread content with replies and nested replies—but does not disclose behavior like pagination, truncation, or how max_replies affects the output.

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?

A single concise sentence that conveys the core output format without filler. It is front-loaded with the resource and immediately clarifies scope with the parenthetical about nested replies.

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 simple read operation with complete schema documentation, the description is mostly adequate. However, it lacks explicit selection guidance against sibling tools and does not describe the return structure beyond 'readable transcript,' which could leave an agent uncertain about how the three parameters shape the output.

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 the parameters are already fully documented. The description adds the notion of 'replies to replies,' which aligns with include_sub_replies, but it does not add meaningful detail beyond what the schema provides.

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 title and description together identify a clear resource: a chat thread, including nested replies, rendered as a readable transcript. This is specific enough to distinguish from the sibling list tool get_chat_threads, but the description does not explicitly call out that contrast or name any alternative.

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 provides no guidance on when to use this tool instead of siblings like read_dm, read_post, or get_chat_threads. The schema hints that thread_id comes from get_chat_threads, but the description itself leaves usage entirely to inference.

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