ig_get_account_insights

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

No annotations are provided, so the description carries full burden. It discloses deprecated metrics and suggests alternatives, which is helpful, but lacks information on authentication, rate limits, error handling, or what happens on invalid inputs. For a tool with no annotations, the behavioral disclosure is minimal.

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 extremely concise (two short sentences) and front-loaded with the core action. Every sentence provides information, but the deprecation notice could be more integrated. Still, it avoids verbosity.

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?

No output schema exists, so the description should explain what the tool returns (e.g., insight values). It does not. It also fails to describe the purpose beyond basic retrieval, leaving ambiguity about the scope (account-level vs media-level). For a tool with 4 parameters, this is incomplete.

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%, so each parameter already has a description in the schema. The description does not add new semantic meaning beyond listing the current valid metrics (already in schema). Baseline 3 is appropriate.

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 states it retrieves Instagram account insights, which is clear from the verb 'get' and resource 'account insights'. The deprecation notice adds clarity on available metrics, but it does not explicitly distinguish from sibling tools like ig_get_media_insights. The name and context help, but no explicit differentiation.

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 versus alternatives. The description only lists deprecated metrics and their replacements, but does not explain usage context, prerequisites, or when to choose this over similar tools (e.g., ig_get_media_insights).

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