threads_get_replies

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

The description adds significant behavioral context beyond the readOnlyHint annotation: it explains that full_tree populates extra fields (root_post, replied_to, is_reply) for tree reconstruction and that default fields differ by mode due to API limitations. No contradiction with 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 a single dense paragraph. It front-loads the purpose but could be improved by breaking into bullet points for modes and field behavior. Still, it is efficient and contains no unnecessary words.

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 lack of an output schema, the description adequately explains the response shape (shared between modes, extra fields in full_tree) and caveats about field availability. Pagination and reverse parameters are covered in the schema.

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 coverage is 100%, but the description adds value by explaining the behavioral implications of the 'mode' and 'fields' parameters, such as why default fields differ and how to override them. This goes beyond mere parameter definitions.

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 replies for a specific Threads post' and distinguishes two modes with specific endpoints and behaviors. It differentiates from sibling tools like threads_get_post (single post) and ig_get_replies (Instagram).

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 explicitly explains when to use 'top_level' vs 'full_tree' modes and mentions default behavior. However, it lacks explicit guidance on when not to use this tool versus alternatives like threads_reply or threads_hide_reply.

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