direct_list_audience_targets

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint, so the trailing 'Read-only' adds no new information. Nothing is said about pagination defaults, result volume, or the shape/limits of the listing, so the description contributes essentially no behavioral context beyond the annotations.

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?

Two short sentences, front-loaded with the resource and scope, with zero filler. The trailing 'Read-only' is redundant given the annotations, which is the only wasted clause.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. But for a 5-parameter, unfilterable-required listing tool, the description omits pagination behavior, filtering semantics, and any usage routing, leaving it only minimally sufficient.

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% across 5 parameters, so the description must carry the load; it does identify the three ID-based filters (ids, ad_group_ids, campaign_ids), which is real added meaning. However, the limit/offset parameters and the mutual exclusivity or combination rules between the ID families are left completely unexplained.

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 (audience targets / retargeting-interest targets) and the three ID families used to scope the listing, so an agent knows what it returns. It does not differentiate itself from similarly named siblings such as direct_list_dynamic_feed_ad_targets or direct_list_smart_ad_targets, which is the only gap.

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 when-to-use statement, no prerequisite, and no named alternative. The only guidance-adjacent text is 'Read-only', which is a trait rather than a usage condition, leaving the agent to infer when this listing should be preferred over the other audience/target list tools.

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