threads_get_conversation

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

Beyond readOnlyHint, the description discloses the required threads_read_replies scope and post access, that the root post is not returned, the ordering and flat-vs-nested representation, and that a parent reply may live on a different page. It also flags reply text as untrusted external content, which is genuine safety context the annotations cannot convey.

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 short and mostly imperative, with the resource scope first, then prerequisites, then pagination, then the safety note. Every clause carries information an agent needs to call the tool correctly — no padding or restated title.

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 shapes need not be explained, and the description still covers authentication, exclusion of the root post, and full-conversation pagination. The only real gap for a 4-parameter read tool is the unexplained `limit` control.

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 carry the load, and it does for three of four parameters: `after` is tied to next_cursor, `post_id` is constrained to the original post rather than a comment, and `account_id` is sourced. The `limit` parameter is never mentioned, leaving its purpose and the 1–100 cap to the bare schema.

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 and resource — read one page of all visible direct and nested replies under a root post — and front-loads the key scoping facts (root post excluded, flat list, newest first). It does not name threads_list_replies or threads_list_pending_replies explicitly, so the agent must infer the distinction from the 'nested replies' phrasing rather than being routed.

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?

It tells the agent exactly where the inputs come from (account_id from threads_list_accounts, post_id from threads_list_posts) and warns against the common mistake of passing a comment ID. Pagination guidance is explicit, including the non-obvious case that an empty items list with a next_cursor can still have more results.

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