get_ig_audience_demographics

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only names the data returned (age/gender, country/city) and does not mention permissions, data recency, read-only behavior, rate limits, or any other operational traits.

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 a single concise sentence with no filler. The core subject and key qualifiers are front-loaded, making it immediately scannable for an AI agent.

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?

An output schema exists, so return-value structure does not need to be described in prose. Still, without annotations, the description omits practical context such as valid breakdown values, permission requirements, or whether the data covers a specific time period, leaving noticeable gaps for an agent deciding how to invoke this tool.

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 description coverage is 0%, so the description must compensate. It partially does by explaining that the breakdown can use age/gender, country, or city, which adds meaning beyond the schema's bare 'breakdown' title. However, ig_user_id is not explained beyond its name and there is no explicit mapping of parameters to the described dimensions.

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 follower demographics—and specifies the main dimensions (age/gender, country or city), which distinguishes it from media/story-level insight tools. The verb is missing from the description, but the tool name supplies the 'get' action.

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 about when to use this tool versus alternatives such as get_ig_account_insigts, audience_overview, or get_page_audience. The purpose implies the use case, but no explicit or even implied comparison to sibling tools is present.

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