yd_audience_targets_get

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

No annotations are provided, so the description carries full burden. It implies a read-only operation via 'Get' but does not explicitly state that it is non-destructive, safe, or idempotent. It also omits any discussion of authentication, rate limits, or side effects. For a potentially limited or data-sensitive operation, this is insufficient.

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, short sentence that immediately conveys the core functionality. Every word is necessary; there is no redundant or filler content. It is well front-loaded for quick scanning.

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?

Despite having no output schema and no annotations, the description lacks details on return format, pagination, error handling, or behavior when multiple parameters are supplied. An AI agent would need additional information to reliably invoke this tool without assumptions.

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 low (25%), but the description adds meaning by mapping the three array parameters (campaign_ids, ad_group_ids, ids) to the filter methods mentioned. However, it does not clarify whether these parameters are combined as AND or OR, or if they can be used together. The client_login parameter is already described in the schema.

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 a specific verb ('Get') and resource ('audience targets'), and specifies three distinct filtering methods (by campaign, ad group, or target IDs). This distinguishes it from sibling tools like yd_audience_targets_add and yd_audience_targets_delete, which perform different actions on the same resource.

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 explain scenarios for using campaign_ids vs ad_group_ids, nor does it mention any prerequisites, combinations, or exclusions. The AI agent receives no help in deciding which parameters to supply.

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