Get Thread Replies

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

Annotations already indicate readOnlyHint=true, so the description's 'gets' is consistent. However, the description adds no further behavioral context like response format, pagination, or rate limits. It provides minimal added value beyond 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 exceptionally concise: two sentences plus an args list. Every sentence earns its place, with no extraneous words. Structure is clear with an args section.

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 no output schema and only three parameters, the description covers the core purpose but omits details about the return format (response_format parameter is missing), pagination, or potential errors. It is adequate but not complete.

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 33% (only response_format has a description). The tool description adds meaning for 'reverse' (reverse chronological order) and mentions 'media_id' as a Threads media ID, but ignores 'response_format' entirely, leaving it undocumented in the description. It partially compensates but misses a parameter.

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 it 'Gets replies to a Threads post,' using a specific verb and resource. This distinguishes it from sibling tools like 'threads_get_post' or 'threads_get_conversation.'

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 vs. alternatives, such as 'threads_get_conversation' which might also return replies. No usage context or exclusions are given.

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