get_ig_story_insights

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states what statistics are returned. It does not mention permissions, data availability windows, rate limits, or whether the story_id must refer to a story owned by the authenticated account.

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 single-sentence description is efficient and front-loads the key resource and metric categories. It contains no filler, though it is more of a noun phrase than a complete verb-driven utterance, which slightly weakens clarity.

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?

Though an output schema exists, the definition lacks essential operational context, such as how to obtain a valid story_id and any prerequisites for access. For a one-parameter tool with zero schema description coverage, this leaves the agent with gaps that siblings like list_ig_stories only indirectly fill.

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?

The schema provides no description for story_id (coverage 0%), and the tool description does not compensate by explaining the expected format, how to obtain it, or whether it is an Instagram media ID. The agent must infer the semantics solely from the parameter name, which is insufficient.

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 identifies the resource (Instagram story) and the operation (returning statistics), listing representative metrics like reach, responses, and navigation. It is distinguishable from sibling tools such as get_ig_account_insights or get_ig_media_insights because it specifically targets stories.

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 is given on when to use this tool versus alternatives, such as list_ig_stories to first obtain story IDs or get_ig_media_insights for broader media metrics. The context is only implied by the name and metric list, not explicitly stated.

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