meta-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return value ('media and comment details') but omits critical information such as pagination behavior, error handling for invalid comment IDs, rate limits, or required permissions/scopes for reading mentions.

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 consists of two efficient sentences with zero redundancy: the first declares the action (getting mentioned comments) and the second declares the return value. Every word earns its place.

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 has only 2 parameters and no output schema, the description adequately covers the return structure. However, for a tool with zero annotations, it lacks important context such as pagination, error scenarios, or the specific Instagram Graph API endpoint behavior that would help an agent handle responses correctly.

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 input schema has 100% description coverage, documenting the comment_id as coming from a mention notification and fields as controlling the return payload. The description adds no specific parameter semantics beyond the schema, meeting the baseline expectation when schema coverage is complete.

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 tool retrieves 'comments where the account was @mentioned' with the verb 'Get', distinguishing it from general comment retrieval tools like ig_get_comments. However, it does not explicitly clarify when to use this versus ig_get_comment (single comment lookup) or ig_get_tagged_media.

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 provides no explicit guidance on when to use this tool versus alternatives like ig_get_comments or ig_get_tagged_media. While the parameter schema implies a notification-based workflow ('Comment ID from a mention notification'), the description itself lacks when-to-use or prerequisite guidance.

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