ad_group_targeting_preview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds only the phrase 'App Store-only' and does not explain what the preview returns, whether it validates targeting, or any side effects or constraints.

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 front-loaded sentence with no wasted words. However, for a tool with a complex nested targeting schema, it is too terse to be structurally adequate.

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?

The tool has four required parameters, nested targeting objects, and an output schema, indicating a fairly complex preview operation. The description does almost nothing to explain the preview semantics, validation behavior, or App Store-only scope, leaving significant gaps beyond structured fields.

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 only 50%, and the description provides no parameter meaning at all. Required parameters such as adGroupId and the nested targeting structure are left almost entirely to the schema, which itself provides only generic descriptions for include/exclude arrays.

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 names a preview operation for ad-group targeting, so the basic verb and resource are identifiable. However, 'App Store-only' is not explained and the description does not clarify what targeting aspects are previewed or how this differs from other ad_group_* preview tools.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The agent is left to infer that this is a preflight check rather than an update or query.

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