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. It successfully discloses the critical behavioral trait that hiding is cosmetic (replies remain accessible via direct link) rather than a security deletion. It lacks disclosure of reversibility, auth requirements, or error conditions, but covers the most important behavioral quirk.

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 sentences totaling 13 words. The first states the action; the second explains the critical behavioral consequence. No filler or redundant information. Perfectly front-loaded and efficient.

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?

For a single-parameter mutation tool without output schema, the description is nearly complete. It explains the domain-specific meaning of 'hide' on Threads. It could improve by mentioning reversibility (via threads_unhide_reply) or success indicators, but the core behavior is documented.

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% (reply_id is documented), establishing a baseline of 3. The description does not add additional semantic context about the parameter format, how to obtain the ID, or validation rules beyond what the schema provides.

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?

Clearly states the action (hide) and target (reply on Threads post). The second sentence distinguishes this from delete operations by explaining visibility semantics. However, it does not explicitly differentiate from sibling 'threads_unhide_reply' or state when to prefer hiding over deleting.

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 explanation that 'hidden replies are still visible if directly accessed' provides implicit guidance about the tool's moderation use case (soft moderation vs removal). However, there is no explicit 'when to use this' guidance, prerequisites, or mention of the 'threads_unhide_reply' alternative for reversing the action.

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