search_demographics

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

No annotations are provided, so the description must carry the behavioral burden. It mentions caching behavior for access_token ('optional - will use cached token if not provided') and defaults, but does not disclose rate limits, authentication requirements beyond the token, or any non-obvious side effects. The read-only nature is implied but not explicitly stated.

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 well-structured with Args and Returns sections. It is concise, with each sentence serving a purpose. However, the main verb 'Get demographic targeting options' could be more prominent at the top. The description is slightly longer than necessary but not wasteful.

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 3 optional parameters, no annotations, and an output schema exists, the description covers the purpose, parameter details, and return format (JSON string with fields). It provides enough context for an agent to invoke the tool correctly without missing critical information.

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 0%, so the description compensates fully. It explains access_token's caching behavior, demographic_class with explicit options list, and limit's default value. This adds essential meaning that the schema lacks, making the tool usable.

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 retrieves demographic targeting options. It specifies the purpose with a verb+resource structure and distinguishes from sibling tools like search_interests by detailing the demographic_class parameter with options such as 'life_events' and 'industries'.

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 implies usage by listing parameters and defaults but does not explicitly state when to use this tool over siblings like search_behaviors or search_geo_locations. No when-not-to-use or alternative guidance is provided, leaving the agent to infer based on parameter options.

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