ig_get_comments

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

No annotations provided, and description only states the function without disclosing behavioral traits like pagination behavior, rate limits, ordering, or whether it returns all comments or only top-level. The agent lacks essential context for safe usage.

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?

Description is a single, clear sentence with no extraneous information. It is appropriately concise and front-loaded.

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?

Tool has pagination parameters (limit, after) but no output schema, so description should clarify return format and pagination usage. Without this, the agent cannot reliably handle responses or implement iteration.

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 for all three parameters (media_id, limit, after). Description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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?

Description clearly states the action (get) and resource (comments) on a specific Instagram media post, effectively distinguishing it from sibling tools like ig_get_comment or ig_reply_to_comment.

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?

No guidance on when to use this tool vs alternatives, such as ig_get_mentioned_comments or pagination strategies. No prerequisites mentioned (e.g., having media_id).

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