direct_list_dynamic_feed_ad_targets

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, so the trailing "Read-only." adds nothing new. The description does not disclose pagination behavior (limit/offset), result ordering, or open-world scope beyond what annotations state, leaving the behavioral picture thin.

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 filler, and the resource is stated first. It is efficient, though bordering on under-specified rather than 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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. Still, 0% parameter coverage plus near-identical siblings mean the description should do more to explain filters and disambiguate; it is barely adequate.

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 carries the full burden. It loosely maps campaign/ad_group/ids to the campaign_ids, ad_group_ids, and ids parameters but gives no array semantics, no mention of limit/offset, and no defaults, leaving two of five parameters undocumented in both places.

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 the resource (DynamicFeedAdTargets) and the filtering dimensions (campaign/group/id), so an agent knows it lists dynamic feed ad targets. However, "Dynamic feed ad filters" is slightly ambiguous about whether it lists filters or targets, and it never distinguishes itself from the near-identical siblings direct_list_smart_ad_targets and direct_list_dynamic_text_ad_targets beyond the entity name in parentheses.

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 stated when-to-use or when-not-to-use guidance. Given three sibling tools that list different ad-target types, the description should route the agent to the correct variant, but it offers no comparison or condition.

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