get_audience_demographics

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'Get detailed audience demographic analysis', with no mention of the read-only nature, response format, rate limits, or any special behavior. While 'get' implies reading, the lack of detail leaves the agent with little insight into runtime semantics.

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?

A single short sentence with no wasted words, front-loaded with the core action. It is easily parsed and appropriately concise, although it adds no structural hints about the schema. It avoids being overlong or vague to the point of uselessness.

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 tool has no output schema and no annotations, so the description should explain what the demographic analysis includes (e.g., breakdown percentages, time ranges) and any prerequisites. It does none of that, leaving the agent with only the parameter schema. This is insufficient for a tool of this perceived complexity.

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 input schema fully describes both 'period' (with an enum) and 'breakdown_by' (with an enum for each item), giving the agent clear parameter meaning. The description adds no additional context or syntax beyond the schema, so the baseline of 3 applies.

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 clear verb 'Get' and a specific resource 'audience demographic analysis', making it understandable. However, it does not explicitly distinguish from sibling analytics tools like get_enhanced_insights or get_my_insights, nor does it mention that it pertains to the authenticated user's audience. It is specific enough but lacks comparative framing.

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 on when to use this tool versus the many other analytics tools in the sibling list. There are no usage conditions, alternatives, or exclusions, so the agent must infer the appropriate context from the name alone.

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