direct_list_dynamic_text_ad_targets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'Read-only' merely repeats structured data. No added context is given about pagination behavior (limit/offset exist), auth needs, or default result size, so beyond the annotations it contributes almost nothing.

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 compact fragments, purpose front-loaded before the safety note, with no filler. It is efficient, though the extreme brevity is also what leaves the usage and parameter gaps.

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 and rich annotations are present, so return format and safety profile need not be restated. Yet for a 5-parameter listing tool with 0% schema coverage, the description omits pagination semantics and how multiple filters combine, leaving it only minimally viable.

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 0%, so the description must carry parameter meaning. It names three of the five filters (campaign/group/id), loosely mapping to campaign_ids, ad_group_ids, and ids, but gives no format or semantics for them and completely omits limit and offset.

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?

States a specific verb (list) and resource (dynamic text ad targeting conditions) with filter dimensions, so the agent knows what it retrieves. However, it does not distinguish itself from the nearly identical sibling direct_list_dynamic_feed_ad_targets, leaving ambiguity about which variant applies.

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 phrase 'by campaign/group/id' implies the tool is used to scope targets to specific campaigns, ad groups, or IDs, giving some usage context. But there is no explicit when-to-use vs when-not guidance and no routing to the sibling feed-targets tool, so the agent must infer the choice.

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