meta-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully indicates ownership requirements ('your Threads post') and the restorative nature of the operation, but omits details about permission scopes, error cases (e.g., attempting to unhide an already-visible reply), and idempotency guarantees.

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, efficient sentence of seven words with no redundancy. It front-loads the action verb and immediately qualifies the scope and target, earning its place without waste.

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 (single parameter, 100% schema coverage, boolean-like toggle behavior), the description adequately covers the essential contract. It could be improved by mentioning error conditions or confirming idempotency, but it is sufficient for correct invocation.

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 100% (reply_id is documented as 'Reply ID to unhide'), so the baseline applies. The description does not add additional semantic context about the parameter format or constraints beyond what the schema provides, which is appropriate given the high schema coverage.

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 uses a specific verb ('Unhide') with a clear resource ('previously hidden reply on your Threads post'). It effectively distinguishes from sibling tools like threads_hide_reply (inverse operation) and threads_delete_post (permanent removal) by specifying the restorative nature of the action.

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 phrase 'previously hidden reply' implies this tool reverses a prior hide operation, providing implicit context for when to use it. However, it lacks explicit guidance on when to choose this over deletion or other moderation actions, and does not mention the sibling threads_hide_reply tool by name.

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