Insights for one IG media item

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

No annotations provided, so description carries full burden. It discloses that metric set depends on media_type and lists specific metrics per type. However, it omits behavioral details like rate limits, required permissions, error scenarios (e.g., invalid media_id, unsupported media type), or whether results are aggregated or per post.

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?

Concise and front-loaded with the endpoint. Lists metric sets clearly, but could benefit from bullet points for readability. No wasted words.

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 no output schema, description is moderately complete for typical use cases. It explains metric variability but lacks parameter semantics, usage context, and error handling. For a tool with 3 required params and complexity, more detail is needed.

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 0% (no parameter descriptions), so description must compensate. It adds value by listing possible metric values per media type, but does not explain the purpose of media_id, via_page_id, or how to use the metric array (e.g., can request a subset, must match media type). Incomplete guidance for a 3-param tool.

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 it retrieves insights for an Instagram media item via GET endpoint, and specifies the metric sets for different media types (IMAGE/CAROUSEL_ALBUM, VIDEO/REELS, STORY). This distinguishes it from sibling tools like ig_media_get (metadata) and ig_user_insights (user-level insights).

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 like ig_user_insights or page_insights. Does not mention prerequisites (e.g., media must belong to a business account, token requirements) or when not to use it.

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