get_audience_demographics

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

Beyond readOnlyHint/openWorldHint, it discloses a real gating rule (needs 100+ followers, or 100+ engagements for engaged/reached), that timeframe only affects engaged/reached, that cities are capped at the top 45, that countries are ISO codes, and that results come back sorted largest first with `unavailable` and `notes`.

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-loaded one-line purpose, then a when-to-use sentence, then structured Args/Returns/Limits blocks. Every line carries distinct information with no filler.

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, yet the description still adds the non-obvious shape facts (sorted descending, ISO country codes, top-45 city cap) and the eligibility limits that would otherwise cause silent empty results. Nothing needed to call it correctly 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 0% – the schema only supplies enums and defaults. The description compensates fully: it defines what each audience value means ('engaged' = interacted in timeframe, 'reached' = saw content), explains 'all' vs specific breakdowns vs 'age_gender' with an example, and notes timeframe's conditional effect.

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: audience demographics with age, gender, country and city breakdowns. This is clearly separable from siblings like get_account_insights and get_follower_active_hours without opening any schema.

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?

Explicitly says when to use it ('when the user asks about their followers' or viewers' demographics: age groups, gender split, top countries or cities'). It gives no when-not conditions or named alternatives (e.g. account insights vs audience demographics), so it stops short of a 5.

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