threads_hide_reply

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: hidden replies remain visible if directly accessed, which goes beyond the simple verb 'hide'. However, it omits reversibility (inferred from sibling) and potential side effects like notification to the reply author.

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?

Two concise sentences: first states the action, second adds an important nuance about visibility. Every word earns its place, and the structure is front-loaded with core purpose.

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?

Adequate for a simple one-parameter tool, but missing context on authorization (who can hide), relation to unhide sibling, and how to obtain reply_id. The presence of multiple siblings in the same server raises the need for more contextual cues.

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?

Input schema coverage is 100% with a clear 'Reply ID to hide' description. The tool description does not add extra meaning beyond the schema, so a baseline of 3 is appropriate. No additional format or acquisition hints are provided.

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 the action 'Hide a reply' and specifies the resource 'on your Threads post'. It distinguishes itself from sibling tools like 'threads_unhide_reply' by explicitly noting that hidden replies remain accessible via direct link, clarifying the non-destructive nature.

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?

No guidance on when to use this tool versus alternatives such as 'threads_unhide_reply' or 'ig_hide_comment'. The description does not mention prerequisites, ownership requirements, or context for hiding, leaving the agent without decision support.

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