demographic_options

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

The annotation already declares readOnlyHint=true, so the description doesn't need to state read-only behavior. It adds context about the return values (age, gender, parental status, income tiers), but does not explain how the optional 'config' parameter affects behavior or disclose any limitations.

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 sentences, front-loaded with the primary purpose and followed by a concise list of return types. No unnecessary wording or repetition.

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?

This is a simple read-only tool with one optional parameter and no output schema. The description adequately covers what data is returned and the intended context. The only gap is the undocumented 'config' parameter, which is a minor omission for a tool of this simplicity.

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 has one 'config' parameter with no documentation (0% schema description coverage), and the description does not mention it at all. With coverage this low, the description must compensate, but it leaves the parameter completely unexplained, providing no guidance on what to pass.

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 function with a specific verb ('Get') and resource ('all available Google Ads demographic targeting options'). It also lists the exact categories returned (age ranges, genders, parental status, household income), distinguishing it from sibling tools like keyword_planner or audience_segments.

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 says it is 'useful for building campaign targeting criteria,' providing a clear use case. However, it does not explicitly compare this tool to alternatives such as audience_segments or audience_recommendations, nor does it state when not to use it.

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