Instagram account insights

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

With annotations already covering the read-only/idempotent safety profile, the description adds substantial non-obvious behavior: a ~90-day data window, follower thresholds for certain metrics, the empty-not-zero return semantics, and the required parameter combination for demographic metrics. These are exactly the traits an agent cannot get from the schema or annotations.

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?

Front-loads the metric scope, then layers constraints in three tight sentences with no filler. Dense but each sentence carries actionable information; nothing is redundant.

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 7-parameter read-only tool with no output schema, the definition covers purpose, retention limits, edge-case return behavior, and the demographic parameter contract. Rate limits and pagination are unaddressed, but nothing essential to correct invocation is missing.

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 71%, and the description compensates by explaining the cross-parameter dependency that demographics require period=lifetime plus metric_type=total_value plus a timeframe and breakdown. It also enumerates allowable breakdown dimensions, adding meaning the schema only partially captures.

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?

States a specific resource and scope: 'Account-level metrics (views, reach, engagement, followers, demographics)'. The 'account-level' framing implicitly separates it from sibling ig_media_insights, though it never names that sibling explicitly, so an agent must infer the boundary.

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?

Provides operational context (90-day retention, 100+ follower requirement) that tells the agent when data will exist, but gives no explicit guidance on when to choose this over ig_media_insights or other insight tools. Usage is implied rather than stated.

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