threads_get_conversation

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

No annotations are provided, so the description must carry the full behavioral burden. It only says 'Get' implying a read operation, but does not disclose specifics such as whether the full thread includes the original post, any limits on thread depth, or pagination behavior. This is insufficient given the lack of annotation support.

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 concise: one purpose sentence plus an Args list. It is front-loaded with the main purpose. The Args list is somewhat redundant with the schema but does add meaning. Overall, it is tightly written without unnecessary fluff.

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's simplicity (one parameter, output schema exists), the description is not entirely inadequate. However, it lacks important context such as whether the full thread includes nested replies, any rate-limit considerations, or a note on how this differs from getting direct replies. It meets only the minimum viable standard.

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 has 0% description coverage, so the description must compensate. The Args section explains 'post_id: The ID of the post to get the conversation for,' adding meaningful semantic context beyond the bare schema type. It also mentions the ctx context parameter, which helps clarify the invocation signature, though ctx is not part of the user-supplied parameters.

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 'Get the full conversation thread for a post,' which is a specific verb-resource pair. It distinguishes this from sibling tools like threads_get_post (single post) and threads_get_replies (direct replies) by emphasizing 'full conversation thread.'

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 explicit guidance on when to use this tool versus alternatives like threads_get_replies. It does not mention exclusions or preference contexts, leaving the agent to infer usage from the name. This is a clear gap.

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