get_demographic_report

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that this is a 'get' report, which implies a read operation, but does not describe data aggregation, filtering behavior, time range handling, or response format. This is a significant gap for a report tool.

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 a single, grammatically clear sentence with no filler. It front-loads the action and resource, making it easy to parse. It earns its place by stating the core purpose without unnecessary words.

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 tool has three parameters, no annotations, and no output schema, the one-sentence description is far from complete. It does not explain what the report contains beyond age/gender, how date range or campaign filtering works, or what the return structure looks like. An agent would need to guess or inspect the schema, which itself is partially undocumented.

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 description adds no parameter semantics. The input schema has only 33% coverage (customerId has a description, but dateRange and campaignIds do not). With such low schema coverage, the description was expected to compensate, but it does nothing to explain what these parameters control or how they relate to the report.

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's purpose with a specific verb ('Get') and resource ('age and gender performance report'). It distinguishes itself from sibling report tools like get_geographic_report and get_search_term_report by naming the exact dimensions (age and gender).

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 no guidance on when to use this tool versus alternatives. There is no mention of suitable use cases, exclusions, or references to sibling tools like get_audience_insights or get_geographic_report. The agent is left to infer usage 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.