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. While 'unhide' implies reversibility, the description fails to explain visibility rules (who can see hidden comments), authentication requirements, or side effects of the operation.

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 single-sentence description is perfectly sized and front-loaded. Every word serves a purpose: the dual verb ('Hide or unhide'), the resource ('comment'), and the scope ('on your post'). Zero redundancy.

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 simple 2-parameter schema and lack of output schema, the description is minimally viable. However, as a moderation tool without safety annotations, it should disclose more behavioral context (e.g., visibility impact, reversibility confirmation) to fully inform agent decision-making.

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 has 100% description coverage with clear explanations for both parameters. The description adds minimal semantic value beyond the schema, merely framing the action contextually as operating on 'your post' without elaborating on comment_id format or validation rules.

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 dual action (hide/unhide) and resource (comment on your post). It implicitly distinguishes from sibling tools like ig_delete_comment (permanent removal) and ig_get_comment (reading) by emphasizing the hide/unhide toggle functionality.

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 implies usage by mentioning both hide and unhide capabilities, suggesting this is for reversible content moderation. However, it lacks explicit guidance on when to choose hiding over deletion (ig_delete_comment) or whether hidden comments remain visible to the commenter.

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