threads_unhide_reply

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the description does not need to repeat those. However, it does not disclose any additional behavioral traits, such as whether unhiding a reply makes it visible to others or if it triggers notifications. With annotations covering the basics, a score of 3 is appropriate.

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, well-structured sentence that front-loads the action and resource. No extra words or redundant information.

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?

The tool is simple with one parameter and no output schema. The description, combined with annotations and schema, provides sufficient context for an agent to understand and use the tool. It could optionally mention the inverse relationship with 'threads_hide_reply', but this is not essential.

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 only parameter 'reply_id' is described in the schema with 'Reply ID to unhide'. The description adds no new meaning beyond what the schema already provides. Since schema coverage is 100%, a score of 3 is baseline.

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 verb 'Unhide' and the resource 'reply', and it distinguishes this tool from its sibling 'threads_hide_reply' by specifying the action is the inverse. The phrase 'on your Threads post' provides additional context.

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 is provided on when to use this tool versus alternatives like 'threads_hide_reply' or 'threads_get_replies'. The description does not mention that it should only be used for previously hidden replies, nor does it exclude other contexts.

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