Get Threads Conversation

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's non-destructive read nature is clear. The description adds value by specifying that it retrieves the full conversation tree (all nested replies), which goes beyond annotations. It does not contradict 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?

The description is extremely concise: two short sentences that precisely convey the tool's purpose and parameters. Every word earns its place. No fluff or redundancy.

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?

Given the tool has 3 parameters and returns a conversation tree, the description provides the core idea but lacks details about the return format or structure (e.g., what fields are in each reply). There is no output schema, so the description could hint at the response shape. However, it covers essential usage, so it is adequate but not comprehensive.

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 input schema covers 3 parameters, but only 'response_format' has a description. The description adds brief explanations for media_id ('Root thread media ID') and reverse ('Reverse chronological order'), which are helpful. However, it omits any explanation of the 'response_format' parameter, which is partially covered in the schema. With only 33% schema coverage, the description compensates somewhat but not fully.

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 clearly states 'Gets the full conversation tree (all replies at all levels) for a Threads post.' This specifies the verb (Gets), resource (full conversation tree), and scope (all replies at all levels). It distinguishes from sibling tools like threads_get_post (single post) or threads_get_replies (likely just direct replies).

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 implies usage: when you need the complete threaded conversation for a post. However, it does not explicitly state when NOT to use it or mention alternatives. For example, if a user only needs the root post, they should use threads_get_post. The description lacks such guidance.

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