audience_overview

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses that the tool returns an aggregated audience overview combining countries, cities, and age groups, and that this is a single-call convenience. This is sufficient for a read-only overview tool, though it omits caveats like time range or data freshness.

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 two short, front-loaded sentences: the first states what the tool returns, the second adds the single-call benefit and the use case. There is no filler or repetition, and every sentence contributes useful information.

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?

For a one-parameter tool with an output schema, the description covers the main output and purpose well. However, it does not clarify the platform context or what kind of page is meant, which matters given siblings for Instagram, Threads, and ad audiences. The page_id parameter semantics are also not addressed.

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 has one required parameter, page_id, and the description never mentions it or explains how to identify the audience target. Schema description coverage is 0%, so the description needed to compensate, but it does not. The phrase 'tes publications' is too vague to map clearly to the required page_id.

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 that this tool provides an audience overview broken down by top countries, cities, and age ranges, and notes that it combines multiple distributions into a single call. This is specific and distinguishes it from single-breakdown sibling tools, though it does not explicitly name alternatives.

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 implies when to use it: when you want to understand who the publications actually address and when you want multiple breakdowns in one call. It does not explicitly state when not to use it or name alternative tools such as get_page_audience or get_ig_audience_demographics.

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