get_audience_demographics

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 does disclose the 12-24 hour data delay and implies a read-only operation via 'Retrieves' and 'Shows'. It omits return-format details and pagination behavior, but for a read-only analytics tool this is acceptable minimum transparency.

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 compact and front-loaded with the core behavior. The data-delay note is relevant. The sentence 'Essential for understanding if you're reaching your target audience' is somewhat general, but it does communicate intended usage without bloating the description.

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 description covers core purpose, the relevant demographic dimensions, a usage rationale, and the latency caveat. However, there is no output schema, and the description does not mention the response envelope, default limits, or how sorting behaves, leaving a few gaps for an agent invoking this tool for the first time.

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 schema already documents all parameters. The description adds plain-language context for demographic types (job function, seniority, industry, etc.), which maps to the demographicType enum, but does not materially extend the schema's meaning.

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 uses a specific verb and resource: 'Retrieves demographic breakdown of who saw or interacted with your ads' and names the segmentation dimensions. It is clear on its own, but it does not explicitly differentiate itself from the sibling tool get_audience_reach, which could overlap semantically.

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 use case ('Essential for understanding if you're reaching your target audience') and a data-delay caveat. However, it gives no guidance on when to prefer this over get_audience_reach or other analytics tools, and no exclusions are stated.

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