ig_insights

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

No annotations are provided, so the description carries the behavioral disclosure burden. It helpfully states the required instagram_business_manage_insights permission and implies a read-only insights operation, but it omits rate-limit behavior, return format, and error conditions.

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 is short and front-loads the core resource and target options. The second sentence about permissions is useful, though the overall phrasing is fragmented and slightly informal.

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 two-parameter read tool with no output schema and no annotations, the description covers the target and gives metric examples plus a permission requirement. However, it leaves gaps around metrics syntax, default behavior, and when to choose this tool over siblings like ig_account.

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 50%: the target parameter is documented in the schema, while metrics is not. The description partially compensates by listing example metrics (views, reach, likes, shares, saves, watch time), but it does not specify formatting, defaults, or whether metrics is optional.

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 that the tool returns Instagram insights for either a media id or "account," and lists example metrics. It distinguishes insights from sibling tools like ig_media_list or ig_comments, though it does not explicitly contrast with ig_account, which could be confused with account-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?

The description offers no explicit guidance on when to use this tool versus alternatives such as ig_account, nor does it state exclusions. The only contextual note is the required permission scope, which is a prerequisite rather than usage guidance.

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