ig_get_account_insights

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

Annotations `readOnlyHint` and `openWorldHint` indicate read-only, non-exhaustive behavior. The description adds valuable context: deprecated metrics, metric_type limitations (most metrics only support total_value), and the ability to choose aggregation shape. No contradictions.

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 two sentences with a note, front-loaded with the core purpose. It is efficient but could be slightly more structured (e.g., bullet list for deprecated metrics). No unnecessary 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 5 parameters, no output schema, and moderate complexity, the description covers metric options, period constraints, and aggregation shapes. It omits JSON return format but is otherwise sufficient for correct 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 coverage is 100% but the description adds critical information about deprecated metrics and the interplay between `period` and `metric`. It clarifies which metrics work with which periods and that `metric_type` has limited support.

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 the tool retrieves Instagram account insights and specifies the effect of the optional `metric_type` parameter. It is distinct from sibling tools like `ig_get_media_insights` which focus on media-level data.

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 provides deprecation guidance and explains `metric_type` behavior but does not explicitly state when to use this tool versus alternatives or mention prerequisites. It assumes the tool is for account-level insights, which is clear from the name.

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