draft_demographic_targeting

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

Annotations indicate not read-only and not destructive. The description adds that the tool drafts and returns a preview, requiring confirmation via another tool. It also explains the effect of the negative flag and the fixed nature of Google's age buckets.

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 clear sections and front-loaded purpose. It is somewhat lengthy but every sentence adds necessary value. Minor redundancy could be trimmed.

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 existence of an output schema (implied), the description adequately covers the tool's behavior, parameters, constraints, and follow-up step (confirm_and_apply). No gaps are evident for an AI agent to use the tool correctly.

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%, but the description fully compensates by explaining each parameter: negative flag, ad_group_id vs campaign_id, and accepted values for age_ranges, genders, parental_statuses, income_ranges. It also notes constraints like at least one demographic list must be non-empty.

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 drafts demographic targeting criteria and returns a preview. It distinguishes from siblings like get_demographic_targeting (which retrieves existing) and confirm_and_apply (which executes the draft).

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 explains when to use the tool (to exclude or narrow demographic segments) and provides constraints like providing exactly one of ad_group_id or campaign_id. It also directs to confirm_and_apply for execution. However, it does not explicitly state when not to use this tool.

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