Demographic targeting

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

Annotations indicate readOnlyHint=true and destructiveHint=false, which aligns perfectly with the description's 'List' action. The description adds context about default behavior and the non-modifying nature of the tool, enhancing transparency without contradiction.

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 tightly written with no redundant phrases. It efficiently covers the tool's purpose, parameter constraint, and output details, while the final sentence about default behavior adds value without bloat.

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?

It describes the output fields (value, negative/positive, status, remove_id) and explains how to use remove_id, which is sufficient for a read-only list operation. Minor gaps remain regarding customer_id usage and potential error cases, but the description is largely complete for the intended use case.

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 clarifies the relationship between ad_group_id and campaign_id (exactly one must be provided) but does not explain the purpose or requirement of customer_id. Since schema coverage is 0%, the description only partially compensates for the lack of parameter documentation.

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?

Clearly states the tool lists demographic targeting criteria (age, gender, parental status, income), which is a specific verb and resource. It is distinguishable from sibling tools that focus on other entity types.

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?

Explicitly instructs to provide exactly one of ad_group_id or campaign_id, which is a critical usage rule. Also explains how the returned remove_id can be used with remove_entity, providing clear guidance for the agent.

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