get_audience_breakdown

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

There are no annotations, so the description carries the behavioral disclosure burden. The phrase 'Results match the Ads Manager optimization event' adds useful consistency information, and the 'get' verb implies a read operation, but the description does not address pagination, data availability limits, or any other behavioral caveats.

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?

Two sentences with no filler. The core capability is front-loaded, and the second sentence adds a meaningful behavioral guarantee. Every element earns its place.

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?

The schema covers parameter syntax well, but there is no output schema and no annotations. The description does not define what 'performance' returns or how results are structured, so an agent lacks some context about the response despite having adequate parameter documentation.

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 100%, so the baseline is 3. The description adds meaning by semantically grouping the breakdown_type enum values into demographics, geography, and platform categories, which helps an agent choose the correct breakdown without needing to infer from raw enum names.

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 a specific action and resource: getting performance broken down by demographics, platform, placement, device, or geography. This separates it from sibling tools like get_campaign_performance or get_creative_performance, though it does not explicitly name those 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?

No guidance is provided about when to use this tool versus the sibling performance or insights tools. The description explains what the tool does but not the context in which it should be selected, and it does not mention any exclusions or alternatives.

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