get_audience_insights

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

With no annotations, the description carries full transparency burden. It discloses the follower floor requirement, how errors are surfaced, and that parameters like metric, breakdown, and timeframe can be overridden. It does not mention rate limits or side effects, but the read-only nature is implicit.

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 front-loaded with the core purpose and is three sentences long. The second sentence is dense with API specifics, but every sentence adds value. It is efficient for the complexity of the tool.

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 the output schema exists, the description does not need to detail return values. It covers main purpose, prerequisite, and parameter behavior. It lacks mention of authentication or permissions, but these are implied by the account parameter context. Overall, sufficient for a tool with an output schema.

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%, yet the description explains several parameters (metric, metric_type, breakdown, timeframe) and their possible values. However, it omits explanation for 'period' and 'account', and the details are somewhat buried in API version notes. Moderate value added beyond the schema.

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 follower demographics by age, gender, country, and city. It uses a specific verb ('get') and resource ('audience insights'), and distinguishes itself from sibling tools like get_account_insights by focusing on demographics.

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 a key prerequisite (>=100 followers) and mentions error handling, but does not explicitly guide when to use this tool over alternatives like get_account_insights or business_discovery. Usage context is implied but not fully stated.

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