ig_get_media_insights

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

With no annotations, the description carries the burden of behavioral disclosure. 'Get' strongly implies a read-only, non-destructive operation, which is helpful. But it does not mention required permissions, ownership constraints, or that insights may be unavailable for some media types or accounts, leaving some uncertainty.

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?

A single, information-dense sentence. It front-loads the core action and resource, then gives illustrative examples. No filler or repetition of schema fields.

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?

For a simple read-only tool with two parameters and no output schema, the description provides enough to select and invoke the tool correctly. It could be slightly richer by mentioning that media_id typically comes from ig_list_media or by expanding the metric examples, but the current text is adequate for straightforward use.

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 description coverage is 0%, so the description must add meaning. It does clarify that metrics refers to insight metrics like reach, likes, comments, and saved, and that media_id identifies the target media item. However, it does not specify accepted metric values or the expected format/source of media_id beyond what the schema's default array already implies.

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 uses a clear verb ('Get') and a specific resource ('insight metrics for a specific Instagram media item'), with concrete metric examples. It also implicitly distinguishes itself from account-level tools like ig_get_account_insights and from media listing tools like ig_list_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 phrase 'for a specific Instagram media item' clearly sets the scope as single-media, not account-level or list-level. However, it does not explicitly name alternatives or state when not to use it, though the contrast with sibling account-insights tools is easy to infer.

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