meta-mcp

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

No annotations provided, so description carries full burden. Fails to disclose error behavior (e.g., comment not found), whether replies are included in the response, rate limits, or required permissions beyond the implicit read 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?

Extremely concise single sentence with no redundancy. However, it may be overly terse given the lack of annotations and output schema, leaving significant gaps that could have been filled with one additional sentence.

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?

With no output schema and no annotations, the description omits critical context: the structure/content of returned comment details, relationship to sibling tools, and error conditions. Insufficient for agent confidence in 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 has 100% description coverage ('Comment ID'), establishing a baseline of 3. The description adds no additional context about the parameter format, valid ID patterns, or that the ID typically comes from 'ig_get_comments' or webhooks.

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?

States a clear verb ('Get') and resource ('details of a specific comment'), but does not explicitly differentiate from sibling tool 'ig_get_comments' (plural) or clarify what 'details' encompasses.

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?

Provides no guidance on when to use this single-comment lookup versus 'ig_get_comments' for bulk retrieval, or versus 'ig_get_replies' for threaded conversations. No prerequisites (e.g., obtaining the comment_id) are mentioned.

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