direct_list_audience_targets

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

The description explicitly labels the operation as 'READ:', which communicates that it is non-mutating. Since no annotations are provided, this is valuable transparency. However, it does not disclose other behavioral traits such as pagination behavior, whether results are scoped by project or campaign/adgroup, or any potential performance implications, so the description only partially covers the burden.

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 sentence that is extremely concise and front-loaded with the key 'READ:' indicator. There is zero redundancy, and every word contributes to conveying the tool's core purpose.

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?

For a tool with 4 parameters, no output schema, and no annotations, this description is too brief. It omits details about response format, parameter relationships (e.g., whether campaign_ids and adgroup_ids are ANDed or ORed, whether 'project' is required), and the nature of the 'retarget conditions'. The description is a minimal placeholder rather than a complete guide.

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 coverage is low (25%), with only 'project' having a description. The description text adds 'for campaign/adgroup', which gives some semantic context to adgroup_ids and campaign_ids, but it says nothing about 'limit' or the 'project' parameter's use in read context. This is insufficient compensation for the schema's sparse 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?

The description clearly identifies the operation as a read of audiencetargets for campaign/adgroup, and the parenthetical 'retarget conditions on groups' adds specificity that distinguishes it from sibling tools like direct_list_retargeting_lists. However, it relies on the tool name for the verb 'list' and uses an API-style reference ('audiencetargets.get') rather than plain language, slightly reducing clarity for unfamiliar users.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that mutation of audience targets is handled by direct_add_audience_targets or direct_audience_targets_state, nor does it state any prerequisites or exclusions. The 'READ:' prefix implies read-only usage, but this is not elaborated.

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